We had a bunch of old issues in Jira, which we went through and archived. We didn't follow the workflow and went straight to archive for the old issues.
We now can't get rid of them out of our active issues log. We read that it was due to going straight to archive, and not following the proper workflow. But, now we don't know how to reverse it to correct the issue. We want to change the issue back to active and then archive the issue properly, so it disappears from active issues list.
Any ideas?
Hi Elizabeth,
what did you do to archive the issues? There's no archiving function in Jira, as far as I know. You can archive a released version and that includes archiving the issues in that. Is that what you have done?
Hi Thomas,
I literally went from In Progress or Waiting on old issues and went straight to Archived. We didn't set up the workflows in Jira, another company did, so I'm not entirely sure how these were set up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, to get an issue out of your "archived" status, you need to have a transition out of it in the workflow, and have permission to use it. It's hard to see from that diagram if there is an outgoing transition.
You'll need to get one of your administrators to edit the workflow - first to see if there is a transition (and then add one if there isn't) and then to check the conditions on it it and ensure you match them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Elizabeth,
it seems, that your workflow has a "Dead End" in the Archived state. There's no transition going out of the state "Archived".
The cause, why your issues are still active in your views is, that they have no resolution set.
So, I would do it like that:
This should result in a new transition for your "dead end issues" that simply adds a resolution, so they disappear from your active isuues list.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nic. There wasn't a transition built in. I have admin access for the workflow, so I can build in the transition. I was speaking to someone in the office about how to build in a transition and we have an error saying we're editing a draft workflow. We've published it, it confirms it's published and then still doesn't let us save a transition
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, that old chestnut.
There's a horrid bug in JIRA that hasn't been stomped on for years. When you have a step with no outgoing transitions, you can't add one while it draft mode.
You will need to copy the workflow. Edit the copy, adding the transition, then create a new workflow-scheme (I would copy the existing one for the project). This new scheme should use your new workflow. Then apply the new scheme to the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nic/Thomas - I've built in the transition to a copied version of the workflow. How do I publish the copy version to overwrite the original? It's not coming up as a draft version. When I click out of the copy I can't see where it goes?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have to exchange the old version of the workflow with the new version of the workflow in the workflow scheme, your project is using.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you're welcome :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This solved my problem also. Thank you! Can we get this bug fixed? I see the comment from scholar web services below, but I don't think I understand the rational for that constraint. Seems more like a bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Nic, is there a "Feature Request" open for the issue you mentioned on June 26, 2018?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Somewhere, but I don't have it bookmarked. It affects only admins who have inherited systems where previous admins were unaware of the bug, there's a relatively easy fix, it's actually a lot of work to fix, and Cloud is moving away from workflow editing in this way anyway. So it's very far down in Atlassian's priorities.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, just found this - Point 3 of the bullet. This sounds like you can't add in a transition in an active workflow and I tried to save a transition to a draft workflow and it says I can't save it to a draft one either....I am new to Jira, so apologies if I'm missing something obvious!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.