Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What are the impacts to scheme/field/issue type housekeeping with Archived Projects or Issues?

Within the instances I manage there are several projects that have issues dating back for years.  The projects themselves can't be archived but I'd like to provide guidance to the project admins to consider archiving some of their issues per Archiving an issue

These older projects also have some niche fields and issues types which we would like to plan to remove or add to our deprecate list.

If I'm searching for field or issue type used in the live/cached instance I could be lead to believe a field is low or not used and decide to remove it (reassigning issues to a new field or issue type during the process).  What happens to the archived issues that may be using the field or issue type?  If some decided to un-archive the issue I can predict there will be errors.  But, maybe Atlassian was proactive and has built in a migration process to the un-archive.  If anyone has tested this or has any input I'd love to hear from you.

Thanks - Tanya

1 answer

1 accepted

1 vote
Answer accepted
JimmyVanAU Community Leader Mar 05, 2021

Hi Tanya,

With archiving issues, there's no impact as the project is still intact, and may well still be in use.

As for the schemes, they also remain attached, so you can't delete or modify them.

See https://confluence.atlassian.com/adminjiraserver/archiving-a-project-938847621.html, and the line:

What happens to a project after you archive it?

Here's a few things you should know about:

Configuration >

  • Archiving a project won't affect the configuration it uses (schemes, screens, workflows, etc.) The configuration remains active and is still shared with other projects. If you change it, the changes will also apply to an archived project once it's restored.

If you did try to remove an issue type only used in archived projects, you won't be able to do so. The issue type is still associated with an issue type scheme, and if this issue type scheme is associated with an archived project, Jira will prevent you from creating a corrupt state. 

 

If I'm searching for field or issue type used in the live/cached instance I could be lead to believe a field is low or not used and decide to remove it (reassigning issues to a new field or issue type during the process).  What happens to the archived issues that may be using the field or issue type?

I haven't come across the custom field situation myself, but my recommendation is to do the cleanup before you archive. Archiving will not allow you to search for issues, so it's very hard to determine the use of a configuration after the fact (other than querying the database). Of course, test everything in a non-production environment.

Hope that helps!

Thanks for the info @JimmyVanAU

I wish I had a non-procduction environment.  We're working on it so this situation may be yet another justification.  :) 

JimmyVanAU Community Leader Mar 05, 2021

I'm amused by the fact that you're running data center without a non-production environment 😅 (or is this what the cessation of server licenses has done, force small customers onto DC).

In your case, I'd test on small projects/schemes first. Good luck!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

196 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you