Issue with Workflow Transition in Business Requirement State
Asked by Soukaina IBALINE:

Hello Community,

I have implemented a workflow and encountered an issue during its operation. The workflow I created follows these steps:

1. **IN BUSINESS REQUIREMENT**
2. **IN BLUEPRINTING**
3. **BACK TO BUSINESS REQUIREMENT**
4. **IN DEV or** **IN PARAMETRAZATION**
5. **IN SIT**
6. **IN UAT**
7. **Done**

From In blueprinting to BACK TO BUSINESS REQUIREMENT" state, the workflow can either go to "IN DEV" or "TO PARAMETERIZATION." Subsequently, the ticket progresses to "IN SIT," "IN UAT," and finally "DONE."

The problem I am facing is that when the state transitions back to "IN BUSINESS REQUIREMENT," the option to go to "BLUEPRINTING" does appear. Instead, only "IN DEV" and "PARAMETERIZATION" wanted to displayed.

Could anyone please advise on how to resolve this issue so that the "BLUEPRINTING" option isn't available when transitioning back to the "IN BUSINESS REQUIREMENT" state?

Thank you for your assistance.

Best regards,

![Screenshot 2024-07-26 at 08.40.02.png](https://community.atlassian.com/t5/image/serverpage/image-id/338087i022EE8F1405290D5/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 08.40.02.png")


Answers:
author: John Funk
body: Hi Soukaina,

Are there Conditions on the transition from In Business Requirement to In Blueprinting? If so, what do those look like?

comments: author: Soukaina IBALINE
body: Hi John ,

No there is no condition on any transaction .


author: John Funk
body: That's strange. I am wondering if it is a caching issue with the browser. You might try clearing your cache or try another browser. Or try with Incognito mode.


author: Soukaina IBALINE
body: ahh sorry my bad , actually , I want if

I have a transition from **IN BUSINESS REQUIREMENT** to **IN BLUEPRINTING** , and I also have a transition from **IN BLUEPRINTING** back to **IN BUSINESS REQUIREMENT**.

When I transition back to the **IN BUSINESS REQUIREMENT** state, I want the options for **IN DEV** and **PARAMETERIZATION** to be displayed. However, the option for **BLUEPRINTING** should not be displayed at this point.


author: Soukaina IBALINE
body: I want in the step which I did Back to business Requirement , when I want to change go to blueprinting to not displayed ![Screenshot 2024-07-26 at 13.47.54.png](https://community.atlassian.com/t5/image/serverpage/image-id/338167i2BE2C3A493BA69FB/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 13.47.54.png")

only go to de and go to parametrazation are displayed


author: Jamie Edmondson
body: Hi [@Soukaina IBALINE](/t5/user/viewprofilepage/user-id/5348405) In your workflow, would you need issues to always go from IN BUSINESS REQUIREMENT to IN BLUEPRINTING first or is it ever possible for an issue to go from IN BUSINESS REQUIREMENT directly to IN DEV or PARAMETRAZATION?


author: Soukaina IBALINE
body: hi [@Jamie Edmondson](/t5/user/viewprofilepage/user-id/5288814)

No, I don't need my issue to go directly to development or parameterization; it must go through blueprinting first.

However, when my issue returns to the business requirement phase, it has the option to go to either development or parameterization, and it shouldn't go back to blueprinting.


author: John Funk
body: So, what you need to do is create custom field, whatever type you like. Then when it moves to blueprinting the first time set that with a value. For instance, a radio button and set it to yes. Then also add a condition going to blueprinting that checks to make sure that the custom field is not equal to the value that you are setting in the custom field. And/or check that it's empty Depending on the type of field that you used.


author: John Funk
body: [@Soukaina IBALINE](/t5/user/viewprofilepage/user-id/5348405) - Any luck?


Tags: cloud

jira-cloud