My team ended up configure an issue type for our projects because they projects in JIRA seem to be permanent...which goes against the very definition of a project. For an organization that may work on 100+ projects a year there is no way we can keep them all listed under projects.
Thanks
Corey
Well, they're not "permanent", but they can be permanent, lasting many years, even as they evolve or fade. And a "project" in JIRA is not just for projects of varying length, they can be simple containers for on-going work that's never going away.
If you need to discard or end projects though, that's not a problem. If a project is ended, do a quick sanity check on it (are the issues all closed) and then you can make it read only, or readable only by admins or an archive user, or even totally invisible (admins would be able to see the project header, nothing more). Or delete it.
Thanks guys...I think that will work. Will check it out in our test environment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When you have finished with a project, go to project settings and take away browse project permission. That will make project invisible to users.
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.