I am working on a project where I think I accidentally created two Issue Type Screen Schemes that I do not need. I would like to be able to view their creation date to verify this and delete the two extra that I just created and do not need and which are not associated with the pre-existing project. Is there a way to view their creation dates? The one of the three that is Associated with the Project I feel is the original and should remain. It is also my understanding that if an Issue Type Screen Scheme is not associated with a project, it is not being used so is safe to remove. Any insight is much appreciated.
Thx!
Hi @Samuel Atkins , welcome to the Community!
Unfortunately there's no way of telling when an issue type screen scheme was created. If the one you wish to keep is associated with your project, then the other two should have a blank value in the Projects column when viewing all of the schemes.
If the issue type screen schemes are not associated with any project, then you will be able to search for them and safely delete them
Ahhh thanks so much Callum. As a new Jira Administrator I am still getting used to the way Jira does certain things. I think the automatically generated naming convention here confused me the most. For instance, the one of the three issue type screen schemes here that has the project associated with it is what I believe was the original issue type screen scheme. However when I added the other two in error, I think it changed its name to :
JIRA Service Desk Issue Type Screen Scheme (2)
and added the two new ones with no project associated as:
Jira Service Desk Issue Type Screen Scheme .....and
Jira Service Desk Issue Type Screen Scheme(1).
What confuses me is I would think it would leave the original one with the project associated as the name without the added numbering, and not bump it down the naming list to having (2) at the end. Any thoughts on this or perspective on the way Jira does this? I mainly want to know if I'm interpreting what happened here correctly.
Thanks so much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A new issue type screen scheme would only be created with a (1) on the end if there's already an existing one without the (1), and there would only be one ending in (2) if (1) was already taken, etc etc.
So if none of the names of these schemes have been manually changed, or if no schemes have previously existed under this name but have since been deleted, then you can assume that the first one in your screenshot is the original.
But then, like you say, if there was only one scheme with this name with a (2) on the end (e.g. if "(0)" and (1) had been deleted), the next two to be created would end with no number and then a (1).
I'm hoping this makes sense, it can get quite confusing with auto-generated schemes!! Regardless of which one was created first, I'd recommend looking into all of those 3 issue type screen schemes and seeing which fits what you're expecting - if they are all just clones of the other then it doesn't matter which was created first and you can delete the other two and rename the main one to whatever you want :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That makes sense. I agree, I think the first one listed without the numbering was likely the original, and the others are identical clones, so I can remove those and keep the original non numbered one after I re-associate the project with it. One additional question I have is can a project be assigned to more than one Issue Type Screen Scheme, or is it only one per?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Samuel Atkins It's only one issue type screen per project, and this is where you map individual issue types to Screen Schemes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.