Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
noresm:usingtheissuetracker [2013-10-22 14:53:20] alfg created |
noresm:usingtheissuetracker [2022-05-31 09:29:32] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Using the issue tracker ===== | ===== Using the issue tracker ===== | ||
| - | === Log in and check what is there === | + | [[https://scrum.met.no/ |
| - | - 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 " | + | |
| - | - 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 " | + | |
| - | - Make sure you can go to agile ==> manage boards and find the NorESM | + | |
| - | - When you are familiar with the dashboard and the scrum board you are OK for now. | + | |
| - | ===Create issues | + | === Why do we need an issue tracker === |
| + | - Oslo and Bergen can easily see what the others are working | ||
| + | - Better traceabilty of code changes (an issue can contain a reference to a code change) | ||
| + | - Better work planning | ||
| + | - Better communication between developers | ||
| + | - Help us work as a team, not just a collection of individuals. | ||
| + | |||
| + | === Log in and check what is there === | ||
| + | - In github: Go to the " | ||
| + | |||
| + | ===Create issues | ||
| - Go to " | - Go to " | ||
| - | - Every other week, we will create a new " | + | - Also add other information to the issue as label (can be e.g. be a project-name). Adding Multiple labels is OK. |
| + | |||
| + | |||
| + | ===Priority definition for NorESM === | ||
| + | - Blocker: We need to solve this immediately. Some project can not be delivered because of this problem. Problem blocks other people from working. | ||
| + | - Critical: Should be solved as quickly as possible. Major problem with product functionality. | ||
| + | - Major: This is the default priority | ||
| + | - Minor: Nice to do this, but not really necessary | ||
| + | - Trivial: Fix this when you have the time | ||
| + | - Not prioritized: | ||
| - | ===Which issues should we add to the scrum board === | + | ===Which issues should we add to different milestones |
| - Find out together with your team which issues are most important | - 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. | + | - Add the issue to the appropriate milestone |
| - | - 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 " | + | |
| ===Working === | ===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. | + | - When you want to start working on something you should always do something which is **included |
| - Go to the task and choose " | - Go to the task and choose " | ||
| - | - Also in the task go to "more actions" | ||
| - | - 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 " | ||
| - | - In svn, I should commit with a comment mentioning the issue, something like "svn commit -m " | ||
| - | - Drag the issue to the " | ||
| + | ===Connection to version control system === | ||
| + | - Mention the task when you commit the fix. For example git commit -m " | ||