⚠️ **Rules Need Revision!** > The Jira rules were somewhat outdated by the upgrade to Jira 4 that changed the dashboard functionality significantly. They have not been updated yet and we await a decision on how much effort it is worth expending before any changes commence. > > I had to make this note a new rule as I could not see a way of adding a note to the site without changing the title. > > * Uly
To help track and prioritise Sys Admin tasks - It has the following key features that help us to work efficiently on the right things in a visible way:
TheSystem Dashboard is the Default Dashboard that is displayed as the Home Page when you enter Jira; it is all about YOU. It contains a summary of the issues that you should be dealing with immediately, those issues you are working on and have queued to work on and those issues that you have requested from others and are still outstanding.
If the task is for SysAdmins you can send an email to the Jira email account with the summary in the subject and the description in the message body. However, if more information is required you will then be asked a quesion in Jira. Do you know how to answer it?
A better way, and the way it must be done for all other projects, is to create an issue in Jira...
On receiving an email from Jira with "Questioned" in the subject or seeing a questioned task in your dashboard, you should open the task .....
The workflow controls how an issue is taken from creation to closure via a Done or Not Done governing who does what at what point. The workflow has several states in which a given number of transitions (actions within a state) can be taken by different people according to their role.
The Reporter is the person requesting the work, will answer any questions on it, review it if required and accept (Close) it once Done or Not Done. The Reporter must respond to questions from the Assignee to keep the workflow going and not hold the Assignee up allowing the Assignee to work efficiently on the right things in a visible way.
The Assignee is the person currently assigned to the task and is responsible for taking it through the workflow to Done or Not Done. The Assignee must maintain the current priority, status and due date (when used) so the Reporter, and anyone else interested or watching, are kept informed efficiently providing complete visibility.
If you don't understand something in Jira and want it explained, simply Create an Issue in the project Jira of type Task [like this](/do-you-know-how-to-create-issues-in-jira. If the question is good for all, it will be made into a rule for all. If the suggestion is approved, it will be implemented. You will, of course, be able to trackthe status of what you create so that we can work efficiently on the right things in a visible way.
Although we use Windows Domain authentication over LDAP, the domain domain is not required and the username must be in all lowercase. The url for SSW is http://jira.ssw.com.au/
Summary: Login to Jira and clear the issues from the top left of your dashboard usually by answering a question or closing.
Jira issues can enter states where it is important that action is taken immediately by either the Reporter or the Assignee. These actions are always quick to do but keep others informed and keep the workflow going.