It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
We have defined a status called "Stalled". Once somthing is stalled, it moves there. Problem is that one looses the context, in which status is it stalled?
Before, in the Classic board, there was this conecpt of "sub-status", where one could "tag" a ticket to be stalled.
Add a customfield, e.g Multi checkbox called Stalled.
Add Swimlane based on Queries and enter a JQL query, e.g. Stalled = Yes
When an issue is stalled, check the checkbox for Customfield Stalled.
Then you have a swimlane with all stalled issues
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
AFAIK, you cannot have sub-status as a standard field. However, you can either add a custom field which says whether the issue is stalled or not or create the Stalled status and add a custom field which will hold the last status, but in this case you will need some workflow scripting plugin (to provide a condition) to get it back to that status.
HTH
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, that is possible, yes, but it is a workaround. And when displaying it in boards and such, it will be cumbersome to visualize it.
From my perspective, conceptually, something is stalled inside another status. Stalled is not a status of itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use a flagging field and do not have to change the status.
The issues will end up under a Swimlane in the rapid board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, seen that, BUT when to define Flagging field, under Greenhopper Configuration, it says it only applies to all the Classic boards.
Have you done it in the new Boards (RapidBoards) of Greenhopper? If so, where do you configure which field is the Flagging field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
According to this [1] it's not yet possible with the rapid boards, but it seems like it will be available soon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.