You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
By the time we get a particular development item through to the Production (Done) column, we no longer care about the bitty technical sub-tasks. Can I configure the column so that only items will show, but not their sub-tasks?
Thank you for your advice!
I created a column called Archived Subtasks. Then I deleted that column. That left me with an Unmapped Status - Archived Subtasks.
When items are transitioned to my Deployed to Prod column that fires a rule:
I have another manually invoked rule which takes all items from my Staging column and transfers them to the Deployed to Prod column. When that happens, the rule above fires. If the item being transferred is a sub-task is is moved over to the Archived Subtasks column, otherwise it is simply left on the Deployed to Prod column. So what happens is, I see all the features ending up in the Deployed to Prod column, while the 'noise' of all the sub-tasks is eliminated.
You could set the board filter to say something like "and !(status = done and issuetype in subtaskIssueTypes())", but this creates the problem that your sub-tasks, as part of their parent issue, cannot be done, so you won't be able to finish anything.
A better option is to live with the fuss on the board but give everyone a quick filter to hide subtasks. People tend to find that quite handy for the whole board, not just the done column.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough Is it possible for me to define a column which is not shown on the Kanban board? I'd call it 'Archive' or something like that and when a parent Item is moved into our Production column I'd fire a trigger which would move all of its sub-tasks into the 'Archive' column. Thus, on the Production column all we'd see would be the parent item cards. Is this possible?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is, if you modify the workflow so that it has an "archive" status you can map into the archive column. You could even not have an archive column at all, so sub-tasks would vanish from the board entirely (although you can only do that with classic projects/boards)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.