Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
noresm:usingtheissuetracker [2013-10-25 11:07:48] alfg |
noresm:usingtheissuetracker [2022-05-31 09:29:32] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
===== Using the issue tracker ===== | ===== Using the issue tracker ===== | ||
+ | |||
+ | [[https:// | ||
=== Why do we need an issue tracker === | === Why do we need an issue tracker === | ||
Line 9: | Line 11: | ||
=== Log in and check what is there === | === 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). | + | - In github: Go to the "issues" |
- | - Verify that you can go to "manage dashboards" | + | |
- | - Add the NorESM default dashboard as a favourite. | + | ===Create issues |
- | - The dashboards shows the epics (large tasks we are supposed | + | |
- | - 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.** | + | |
- | | + | |
- | + | ||
- | ===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 |
- | + | ||
- | ===Issue type definition for NorESM === | + | |
- | An issue can be created as one of several types. In NorESM we will use the following definitions: | + | |
- | + | ||
- | - EPIC: A task which demands some man-months. For example in the EVA-project, a task is an epic. An epic consists of several stories. See https:// | + | |
- | | + | |
- | - TASK: A story will have several sub-tasks. They are created inside the story (open the issue ==> more ==> create sub-task). The tasks will last some man-days and it is the tasks which will be added to the sprints. | + | |
- | Take the example of the EVA project proposal: "Task 2.1 Ocean dynamical core development" | ||
===Priority definition for NorESM === | ===Priority definition for NorESM === | ||
Line 38: | Line 27: | ||
- | ===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 story (or epic) and convert the issues into sub-tasks of the story. 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 " | ||