You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am using Jira Cloud Premium.
In Advanced Roadmaps, you have the feature where you can remove issues from the plan by selecting issues and then selecting Bulk Actions-> Remove from plan. This doesnt delete the issues, but hides them from the plan, and you can see all issues you have removed in this way by going to Plan Settings->Removed issues.
I would expect this view to then allow you to permanently delete some or all of those removed issues, but all it allows you to do is "Re-include" some or all of them. The problem this leads to is that these issues, although hidden from the plan, are turning up in dashboards.
You can go through each issue individually and delete them by clicking on the issue key to open up the edit issue screen, but that is tedious when you have 10s or 100s of removed issues.
Does anyone know of a way to bulk delete removed issues? I was thinking to filter for them and then do Bulk Change, but I cant find any way they are marked as Removed Issues to be able to filter for them.
Because of this, to me, the Remove from plan function seems pretty pointless, and more detrimental than beneficial, as its the most intuitive function users will use to delete issues. No matter how much training you give users to use Bulk Actions->Bulk change in Jira->Delete, as soon as they see Remove from plan they are going to click it, and then as an admin you'll be wasting hours individually deleting issues one by one.
This may lead to a philosophical discussion somehow, but as a rule of thumb, try not to delete issues at all. They have been created for some reason in the first place.
From what you describe, it almost seems as if you are trying to use your plan as a tool to review ideas and then only want to keep those that you are actually going to work on.
While it definitely makes sense to remove items from view that you are not going to work on (for now or indefinitely), it also makes sense to keep a record of ideas that have been raised at some point, as well as decisions that have been made not to do certain work. Rather than deleting those from your Jira instance (where they are gone and lost forever without any record of their existence), it is much more common to add a transition (and/or status) to your workflow to soft delete them. That means: keep them in Jira, but mark them as cancelled or rejected.
By doing so, you can easily exclude them from your dashboards and other places in Jira where you don't want to see them, but you will be able to retrieve them at any point in time.
As a final side note to the features in Advanced Roadmaps: a plan is a layer on top of Jira. Issues are not stored in your plan, they are associated with it so they can be visualized there and manipulated via the planning features. They remain stored in Jira, in the project they were originally created in and with the attributes (fields, status, permissions, ...) associated with that project. So removing an issue from a plan only breaks that association, it doesn't do anything to the issue itself and so you can't use a (former) reference to a plan in any way to query for issues not delete them.
Hope this helps!