How do I hide closed issues when grouping by subtask

[Jonas Stenberg]

We use the Board view during daily standups and the best view for that is "Group by" subtask.

It is possible to expand and minimize issues wich is great but the problem is that it is not possible to see on a minimized issue that the issue is closed. I would like that the issue is either displayed with a strike-through as it is or simply hidden from this view with a filter or something. Is this possible to achieve?

[Satish_Kumar]

If the tickets are that old, then one workaround is to exempt them from SLAs (Using JQL in goals of SLA definition) ?

[Mark Lock]

We had this issue too. Couple of workarounds I have discovered seem to work.

Set multiple stop conditions, ie resolved and closed statuses - it may be your imported issues never entered resolved, but are marked as "closed" or similar

or add a created after condition to your jql to filter out imported issues.

[Vincent Naudion]

hi @Mark Lock could you provide an example of condition which will stop SLA counter on CSV import? I've tried several case but nothing affects.

Thanks a lot.

[Dept]

@TAS what you suggest appears to be what is happening, the trigger for these imported tickets is never fired.  If we open and then close an imported ticket then the timers are stopped, but when bulk transitioning all these tickets the SLA is well and truly exceeded - some of our tickets that were imported were from 2008, the SLA is then calculated from 2008 to the date of transition not the date of the closing of the ticket.

What configuration information would be helpful? We are currently using the default SLA start/stop/pause conditions (eg for the Time to Resolution stopping on Entered Status: Resolved).

[teilor_soares]

Is hard to tell exactly how to solve your problem without seeing the tickets you imported and the configurations you have to calculate SLAs, but I think this problems is happening because this tickets never fired the action which stops the SLA time.

If you reopen one of this tickets and close it again, it will the SLA counter stop? And if the reporter add a new comment to the ticket?

One possible solution to this problem would be a bulk edit in this tickets do fire the action which stops the SLA counter.

We already have a bug report regarding this odd behavior in https://jira.atlassian.com/browse/JSD-1221

If you need to share you configurations to achieve this bulk edit (if possible), I would recommend to you to open a ticket in our support channel.

Cheers!
Regards