Differences

This shows you the differences between two versions of the page.

--- map_suite_jira_guide [2017/04/26 19:38]
benbai [Project Types / Categories]
+++ map_suite_jira_guide [2017/04/28 03:27] (current)
marklee [Create a New Issue Screen]
@@ Line 1: / Line 1: @@
 ====== Map Suite JIRA Guide ======
-This guide shows how to manage Map Suite projects and issues in Jira. [[https://thinkgeo.atlassian.net|ThinkGeo Jira]] also has Curtus View projects on it, and this guide only cares about Map Suite Projects and issues.
+This guide shows how to manage Map Suite projects and issues in JIRA. [[https://thinkgeo.atlassian.net|ThinkGeo JIRA]] also has Curtus View projects on it, and this guide only cares about Map Suite Projects and issues.
 ===== Project Types / Categories =====
-This section introduces how the Map Suite projects are organized.
 After signing in [[https://thinkgeo.atlassian.net|ThinkGeo JIRA]], goto Projects/View all projects and you will see all the projects and categories.
@@ Line 11: / Line 9: @@
   * **//Project type / Business//** None of the projects are under this group so far;
-Categories: (I renamed it to Map Suite Products from ThinkGeo Products, please update the snapshot accordingly. )
+Categories:
   * **Map Suite Products: ** Map Suite products line, including iOS, Android, GIS Server etc.
   * **ThinkGeo Internal Projects: ** The internal projects, like single point, demo etc.
@@ Line 18: / Line 16: @@
 {{:jira_projects.png? |}}
-===== When to create a new project or task =====
+===== Create a project=====
-We don't create a new project every often. When a new project launches, One of us including (Howard, Johnny or Mark) will create one for your need. So please don't touch the Create new project button unless one of us asks you to do it for now.
+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.
-Everyone in ThinkGeo need to create a new task depending on the project you belongs to. We have different auth to manage the tasks. Generally works as following. (We could add more items in this section later)
+===== Create an issue =====
+====New Issue Screen====
+Everyone working on Map Suite needs to create a new task if either of the following requirement is met:
+  * The issue will take more than 2 hours.
+  * The issue will affect the product, for example, change the source code.
+  * The issue needs to be seen by a user, for example, update a sample, update a wiki page.
-  * Most tasks must come from our forums. So the support team has following reason to create a new task.
-      * From forums post/ticket when it spends more than two hours.
-      * Found a bug when creating samples by user's requirement.
-      * Found a bug when working on some enhancements.
-  * Dev team will create tasks for following reasons
-      * A new bug is assigned from support team
-      * A new enhancements for a specified product
-      * A memo note for short / long term tasks
-  * Professional service team manages their tasks by their rules
-===== Create a new task =====
+==== Create a New Issue Screen ====
-Let's take a bug report from forum for example. In the morning, reviews the forum and notices a bug in Android Edition report from customer. If it is worth to fix, we want to record this bug in our Jira system, so that we could find it back for the next release log. So the first thing is to navigate to a corresponding project.
+Everyone has the permission to create an issue, do please create it within the correct project.
-  * Goto https://thinkgeo.atlassian.net
+{{::jira_create_issue.png?|}}
-  * Navigation bar -> Projects -> View all projects
-  * Find Android project and enter in
+  * **Issue Type:**
+    * //Task:// Task that needs to be done
+    * //Bug:// Problem that impairs product or service
+    * //Improvement:// Enhancement for product or service
+    * //Sub-Task:// Smaller task within a larger piece of work
+    * //Story:// Functionality request expressed from the perspective of the user
+    * //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.
+    * 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.
+    * Where it comes from
+    * The detail description
+    * What causes it if you know
+    * The solution you expected
+  * **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.
+  * **Assignee:** If you don't know who is the resource, just leave it unassigned.
+Fill the other fields if needed, then click Create button to create the issue.
+====Issue Work Flow====
+A JIRA workflow is the set of statuses and transitions that an issue goes through during its life cycle.
+{{:jira_workflow.jpg?|500*500}}
-Now that, we could see a board of Android projects. It contains 6 columns which apply the same project template like the other projects.
-A JIRA workflow is the set of statuses and transitions that an issue goes through during its life cycle. The resources in this section will help you extend workflows in JIRA. For example, you could create custom elements (functions, validators, etc) that can be added to workflows.
-Below is our currect workflow:
-{{:jira_workflow.jpg?|}}
 === Backlog ===
@@ Line 69: / Line 89: @@
   * Closed->Backlog: Redo this issue.
-Let's continue. Click the Create button on the navigation bar to create an issue. There are some options to be aware of.
-{{::jira_create_issue.png?|}}
+===== Track an issue =====
+====Create an Original Estimate====
-  * **Issue Type:** We will use following types for higher priority. An issue in JIRA can represent different things, depending on how the organisation is using JIRA. For example, it could represent a software bug, a project task, a helpdesk ticket, a leave request form, etc. The resources in this section will help you extend issues in JIRA. For example, you need to add content to the View Issue page or action issues programmatically.
+Before moving an issue to TODO list, you need to enter the Original Estimates. And as you work on it, you need to adjust the Remaining Estimates as necessary.
-    * //Task:// Task that needs to be done
-    * //Bug:// Problem that impairs product or service
-    * //Improvement:// Enhancement for product or service
-    * //Epic:// Large piece of work that encompasses many
-    * //Story:// Functionality request expressed from the perspective of the user
-    * //Sub-Task:// Smaller task within a larger piece of work
-  * **Summary:** It is the major title of this issue and try to best to simplify your sentence and cover the issue point.
-  * **Description:** Should have more details for your issue, including following items. The more the better.
-    * Where it comes from
-    * The detail description
-    * What causes it if you know
-    * The solution you expected
-  * **Priority:** If you don't know, just leave it default. But if it is not urgent, please use Trivial.
-  * **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 assign to the team leader.
-Then click Create button and the task is created.
-===== Estimate issues =====
-Before a sprint starts, you need to enter the Original Estimates of your issues. And as you work on the issues during the sprint, you need to adjust the Remaining Estimates as necessary.
   - Navigate to the Backlog of your desired board.
   - Click the issue that you want to set the Original Estimate for.
   - In the Issue Detail View, type your estimate in the Estimate field.
 {{:jira_estimate.png |}}
-===== Log work =====
-Once you have started to work on a specific issue, you need to log your work by following these steps:
+==== Log the Hours ====
+Once have started working on a specific issue, you need to log your hours everyday if there is any update.
   - Select the issue you want to log time on.
   - Go to More > Log Work.
@@ Line 105: / Line 105: @@
 {{:jira_log_work.png |}}
-===== Summary =====
-As we are going to use JIRA for all the issues, we must follow this workflow when using JIRA.

User Tools

Site Tools

Differences

Page Tools