This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
map_suite_jira_guide [2017/04/27 01:57] marklee |
map_suite_jira_guide [2017/04/28 03:27] (current) marklee [Create a New Issue Screen] |
||
---|---|---|---|
Line 18: | Line 18: | ||
===== Create a project===== | ===== Create a project===== | ||
- | We don't create a new project very often. Please let Howard, Johnny or Mark to do it if you want to create a new one. They know how to set up the correct workflow/issue screen schema to the project. | + | We don't create a new project very often. Please let Howard, Johnny or Mark do it if you want to create a new one. They know how to set up the correct workflow/issue screen schema to the project. |
===== Create an issue ===== | ===== Create an issue ===== | ||
Line 38: | Line 38: | ||
* //Bug:// Problem that impairs product or service | * //Bug:// Problem that impairs product or service | ||
* //Improvement:// Enhancement for product or service | * //Improvement:// Enhancement for product or service | ||
- | * //Story:// Functionality request expressed from the perspective of the user | ||
* //Sub-Task:// Smaller task within a larger piece of work | * //Sub-Task:// Smaller task within a larger piece of work | ||
- | * //Epic:// Large piece of work that encompasses many. We don't need to have it for most cases. | + | * //Story:// Functionality request expressed from the perspective of the user |
- | (Story kind of overlaps with Task/Bug/Improvement. Story is more from user's perspective but Task/Bug/Improvement is from developer's perspective.) | + | * //Epic:// Large piece of work that encompasses many. We don't need to have it for most cases. |
+ | |||
+ | * Note 1: Story overlaps with Task/Bug/Improvement a little bit. Story is more from user's perspective but Task/Bug/Improvement is from developer's perspective. | ||
+ | * Note 2: Most likely, A story will be specified by different Task/Bug/Improvement, in this case we want to hook up those Task/Bug/Improvement with that story by using linked issues. | ||
+ | |||
* **Summary:** It is the major title of this issue and try to best to simplify your sentence and cover the issue point. | * **Summary:** It is the major title of this issue and try to best to simplify your sentence and cover the issue point. | ||
+ | * Fix one bug, set JIRA’s title **Fixed XXX**; | ||
+ | * Improve products, set JIRA’s title **Improved XXX**; | ||
+ | * New feature, set JIRA’s title **Supports XXX**. | ||
+ | |||
* **Description:** Should have more details for your issue, including following items. The more the better. | * **Description:** Should have more details for your issue, including following items. The more the better. | ||
* Where it comes from | * Where it comes from | ||
Line 48: | Line 56: | ||
* What causes it if you know | * What causes it if you know | ||
* The solution you expected | * The solution you expected | ||
- | * **Priority:** If you don't know, just leave it default. But if it is not urgent, please use Trivial. | + | * **Priority:** It has 4 levels, Blocker, Critical, Major and Minor. We don't use Blocker unless it's serious important. Leave it as default priority if you are not sure when creating a ticket. |
* **Attachment:** If you have a sample to recreate the issue or a prototype for your idea, please attach it here. | * **Attachment:** If you have a sample to recreate the issue or a prototype for your idea, please attach it here. | ||
* **Assignee:** If you don't know who is the resource, just leave it unassigned. | * **Assignee:** If you don't know who is the resource, just leave it unassigned. | ||
- | Then click Create button and the task is created. | + | Fill the other fields if needed, then click Create button to create the issue. |
====Issue Work Flow==== | ====Issue Work Flow==== |