We are moving forward with new project configurations in JIRA and want to keep all the history in our old project but prevent anyone from using them for future tickets. What do we have to do? Is it possible to in some way inactivate old "retired" JIRA projects in such a way that no new tickets can be entered for them but old tickets in them can still be accessed (read only perhaps)?
Gabriella is right. One thing to consider, if you're using an older version of JIRA before Atlassian introduced the "Transition issues" permission: Make sure that transitions can't be triggered!
Again, just relates to older versions but in these cases you had to add conditions on all transitions because even if people just had the browse project permission they could still transition issues!
Cheers
What we've done in our instance is to create a new permission scheme, e.g. "Archived", and remove everyone from the Create permission. (In our case, we also removed the ability to transition, edit, and comment on tickets.) Then apply that permission scheme to the project.
This removes the ability for anyone to create issues in your project, while still allowing them to browse.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's just a matter of updating the project's Permission Scheme to remove everything except "Browse Permission". Create a Permission Scheme called "Read Only Permission Scheme" and apply it to inactive projects since JIRA does not have a default feature like this.
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.