This is possible when you are writing your own custom field with this behaviour or a listener that listens to issue update events- although these might be overkill for your case. What are the specific requirements for your use case?
If the user unchecks the box, would it be necesary to roll back to the previous state? How many states are there in your workflow and from which states can the user transition the ticket? Is it really no option for a user to click on a transition button in the bar of the ticket?
Thanks for your reply!
Yes, it is our customer field. My scenario is, when user open an urgent issue which should be fixed ASAP, we would like to use another status instead of 'Open', but it looks like JIRA workflow doesn't support two initial status. So we would like that JIRA could automatically change to another status if user enable the customer field after the issue open. Then a review will review this issue to decide if this issue needs to be fixed ASAP. So if this checkbox will be unchecked, no need to roll back to the previovs status. Do you think if it is possiable to do it? Thanks
Do you need the other state for filtering the list of issues that might need fixing ASAP?
If that is the case, you could also create a filter that checks for the open state AND a checked value on your specific custom field. To do this, go to your issue navigator and add the field to your query by clicking "More" and selecting it from the list. More information can be found in the JIRA Basic Search Documention.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs