I want users to be able to edit certain fields (not all) for issues in any state. I can create a global transition, but the end state must be defined. I want the end state to be equal to the current state. In other words, I just want the user to edit fields but not change state.
I am able to set the end state to "-1" by manually editing the workflow XML but this prevents me from using the UI for modifying the workflow in the future. If I do use the UI, the end state for this global transition is changed to a real state (16).
How do folks implement a "restricted edit" function for their users?
There isn't such a thing as a "global transition". Things like edit and comment are not a function of workflow. All workflow transitions have a single endpoint (otherwise you could define many -> many, which is nonsense)
To do this, you have to add a transition to each step you want your restricted edit to be available in.
The other option is to write some code to provide your restricted edit outside the workflow, like the standard edit.
Ha. That's my thread. It answered a different question I had, but then wandered into this restricted edit functionality. My trouble is the "-1" transition end state. This is not accepted by the JIRA workflow UI (normal or designer) and reverts without telling you. I don't want to be stuck in a position where I have to edit the workflow xml every time I make a change.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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