We have projects on which work stops due to company project reprioritization.
In an ideal world I might just close those issues with a resolution of "project frozen" and forget about them. I'd have to modify the workflow to allow that transition from anywhere as the issues are in various states.
However, the project *may* reawaken.
I am looking for ideas on how set this up so that we can handle that (reawakening) without examining each issue. If the project "unfreezes" I'd like to put things back where they were, i.e. to the previous state. I'd like to filter for frozen issues under some criteria, and in one operation restore their state.
Note that the issues may be spread across Jira projects (typically not, but it could happen) where other issues are not frozen.
Assuming there is no straightforward solution...
Some possibilities I see
I guess that you already narrowed all the approaches. In case you do not know: you can do bulk transition or edit based on a filter/JQL https://confluence.atlassian.com/jiracoreserver072/editing-multiple-issues-at-the-same-time-829092790.html
I think you already defined the approach:
- create and store a filter
- add CF and store current state to it for filtered issues
- update workflow by adding new state and forward/back transitions for it
- do bulk transition for the issues in the filter
- when needed to restore filter by separate states in the CF and do individual bulk transitions for each state
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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