New to Jira, a little lost

Question

I am new to Jira and have loaded all the "projects" that I had in my head and on paper to be able to keep track of them. I have now started adding a task and completing them and the project is now complete. My question is, how do I archive the project and then how does my boss log in to see my "completed/archived" projected.

Jessie

Gurpreet_cqt1ju · Answer

i would like to take back my initial answer because there is a way you can ARCHIVE project in JRIA.

while there is no direct option that says ARCHIVE(like we have for delete project), you can create a permission scheme in which all permissions are empty and assign to the project which you want to archive. once you do that , no one (except administrators) can see the project or its issues.

here are the details (go in the very end where it says hide(archive the project)

https://confluence.atlassian.com/adminjiracloud/creating-editing-deleting-and-hiding-projects-844500729.html

Joe Pitt · Answer

Welcome to JIRA.  As a new comer here are some pointers that often come up as you work with JIRA.

JIRA permissions

First, by default JIRA has a horrible permission scheme that violates security best practices by allowing everyone that can logon to do just about everything.

JIRA works by GRANTING access. You can't restrict access. By default, it grants access to the group used to logon (used to be JIRA-users but may be different on your version).  This is where users are getting the access from.

* The FIRST thing you need to do to get control is to remove any groups with logon privileges from the permission scheme unless you absolutely want everyone to have that permission.
* Then I suggest you setup Project Roles for the various functions like, tester, QA, Browse Only, etc.
* One permission scheme will cover almost all projects. The project admin controls project role membership

This may be a big effort, but it will pay off down the road by making it easy to control access.

Most of the 'old timers' use project roles. It meets the best practice for security and gives complete control to the project lead for access to their project. JIRA comes with many project roles, but you can add more if you have a special need.

Do not delete issues. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. Deleting issues will come back and bite you when it is the most inconvenient. I suggest closing with a resolution value of Deleted anything you want to delete. I implement a special transition only the project lead can execute and it requires filling in a reason field from a select list (such as entered in error, OBE, Duplicate, Other) and explanation text.

Missing issue numbers will eventually cause a question about what it was and why was it deleted even if it was done properly. Missing data always brings in the question of people hiding something that may have looked bad.

The only viable way to restore an issue is to create a new instance of JIRA and restore a backup that has the issues. Then export them to a csv file and import them to your production instance. You will lose the history.

Do not delete users

Users should be made inactive not deleted. JIRA uses a pointer to the user’s DB entry to display user information. If you delete a user when you open a JIRA issue the user worked on anywhere the user that would be displayed will cause a SQL error. Even if the user never logged on, if they were assigned a ticket the history of the ticket will get an error when you display it.

Vasiliy Zverev · Answer

There is a work around we use to define if project is complete or not.

So, in every project we create an issue to store information about all project.

When project comes to the end this issue also closes.

Try to use this aproach.