This is an old revision of the document!
Using the issue tracker
Log in and check what is there
- Log in to JIRA (scrum.met.no) using the same user-name and password that you use for svn access (This is the LDAP password at met.no, external users have an external LDAP password).
- Verify that you can go to “manage dashboards” and search for dashboards created by Alf Grini. You should find the NorESM default dashboard.
- Add the NorESM default dashboard as a favourite.
- The dashboards shows the epics (large tasks we are supposed to solve for the next version) together with some other information. It the NorESM “homepage” at JIRA.
- Make sure you can go to agile =⇒ manage boards and find the NorESM scrum board. This board is shared between Oslo and Bergen, and it is our way of communicating what we are working with right now.
- Note that the scrum board can be filtered by components, so it is easy to look at only MICOM issues or only cam-oslo issues.
Create issues and start working
- Go to “create issue”. Note that in NorESM, the issues are different components. Make sure you select the right component for your issue.
- Every other week, we will create a new “sprint”. That means that the scrum board will be refreshed. (see below)
Which issues should we add to the scrum board
- Find out together with your team which issues are most important
- Try to compose a sprint so that the product (NorESM) is more or less usable at the end of the sprint.
- If a task requires more than 3 days of work, it should probably be splitted into sub-tasks. Create an epic and convert the issues into sub-tasks of that epic. Go to issue, more actions and “convert to sub-task”.
Working
- When you want to start working on something you should always do something which is in the sprint. Those are the tasks that the team has defined as most important.
- Go to the task and choose “assign” and “assign to me”.
- Also in the task go to “more actions” and “start progress”. You can also just drag the task over in the “in progress” column in the scrum board
- When the task is finished, there should always be a comment saying which changeset in the version control system which solved the problem. For example if I solve task “NE-10”, I should comment in JIRA “this taks was solved by svn changeset nn”.
- In svn, I should commit with a comment mentioning the issue, something like “svn commit -m “solved issue NE-10 by removing possible divide-by-zero””
- Drag the issue to the “resolved” column when the problem is solved.