Can I hide all stories whos subtasks all are hidden?

[Jimi Hullegård]

Hi,

We use a few custom quick-filters in our project, and in the Active Sprint board they work great to filter out sub-tasks. But when we switch to the Backlog board they are not really working as we want them to, and I can't seem to find a way to solve that. Because what we want is to hide all stories, whos sub-tasks are all hidden.

For example, let's assume the following:

• We have one story PROJECT-1, with the subtasks PROJECT-2 and PROJECT-3
• PROJECT-1 has status "In progress", PROJECT-2 has status "Resolved" and PROJECT-3 has status "Ready for test"
• We have a quick filter: status not in (Closed, Resolved, "Ready for test")
• We are currently viewing the Backlog board

Expected/wanted behaivor:

PROJECT-1 is hidden, becaues all it's subtasks are hidden by the filter.

Actuall behaivor:

PROJECT-1 is shown.

Is there any way to make Jira behaive like we want in this case? Either using some project setting, that automatically hides a story when all it's subtasks are hidden (but preferably the special case of a story without subtasks could be exempted from this rule), or with some JQL magic that we can apply to the filters where we want this behaivor.

Regards
/Jimi

[MJ · Accepted solution]

I do not think it is possible to configure this. Depending on your exact needs, you could choose to create 2 separate transitions. The first transition you limit to be performed by the people for which you want the field to be required. The second transition you limit to be performed by the other users, in which you do NOT make the field in question required. I think you can only configure this in any transitions beyond the create issue transition. Please have a look at this page, and in particular the conditions and validators section.

[Joe Pitt]

Do you want to control it during creation or later in a transition? If On Demand allows the JIRA suite utilities you can do it on transitions by having a different transition setup for the select people. They would need to be part of a group or role you can limit the transition to. You'd want to exclude them from the allowed group for the 'required field' transition to avoid confusion of which one to use. If during creation I belive you're out of luck.

[Nic Brough -Adaptavist-]

No.

You can't even do that on Jira if you host it yourself.

There are plugins that might help you - behaviours and the field security plugin are the two that spring to mind, but I don't think either are usable in OnDemand.

You do have the option of controlling edits by doing it all in the workflow instead though - you remove the fields from the edit screens and create transitions that can only be used by the two sets of poeple, using validators to make it mandatory for one set of users. Rather fiddly though.