nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issues using filtering/archiving issues on backlog

Bridget O_Hare

Hi all,

I know this has been asked a fair few times and I feel like I've gone through most of the posts on the community but I'm still having issues applying filtering to my backlog.

For context, my team migrated from Trello to Jira Software. One feature that we did utilise in Trello was the ability to archive cards. I'm aware there is no way to 'archive' a card in Jira. My initial workaround was to add these cards to a sprint and complete the sprint in order to remove them from the backlog. This ultimately impacts my reporting and is a annoying workaround.

We do want to have a record of issues on Jira that we are not considering at this point in time or, issues that we have considered but decided against in our planning/scoping process.

I tried to create a label called 'not-going-to-do' and applied this to the tasks that I want to filter from the board. Though when creating the filters via JQL I cannot for the life of me get this to work:

project = UPG and issue != "not-going-to-do"

When filtering this way, the issue with the applied label is still appearing in the list.

Am I missing something here? I like Jira but not having the ability to archive or hide issues easily is really turning me off the platform altogether.

Accepted answers

All comments

John Funk

Hi Bridget,

We actually created a couple of statuses to handle things like that. We have a Discard status for cards that never made it out of the Backlog and that we decided not to do. We have an Abort status for cards that got started but then we decided we were not going to finish them. Both of them have a status category of Done (just like Done does) but we set the Resolution field to Obsolete when we transition a card to one of those statuses. Then the filter on the board itself will not show cards in the Discard or Abort statuses.

For your query above you probably need something more like:

project = UPG and and labels != "not-going-to-do"

Bridget O_Hare

Hi John,

Thanks so much for your reply. I'm struggling with creating a new status. According to my issue types, the 'Status' field was created by Jira and cannot be edited:

Screenshot 2020-03-18 at 10.40.17.png Am I missing a step here?

Also, the filter 'project = UPG and and labels != "not-going-to-do" cannot apply due to the 'and and'.

John Funk

sorry, that was a typo - take out one of the "and"s and try it again.

Is this a next-gen project?

If you are wanting to add a new status, that is done in the workflow. Edit the workflow and add in the new status and the appropriate transitions. Once that is done, you can add the status to the board.

You might start here was some guidance:

https://support.atlassian.com/jira-software-cloud/docs/what-are-jira-workflows/

Bridget O_Hare

Hi John,

Yes, this is a next-gen project. Are we able to assign new workflows to next-gen projects?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software