This guide shows how to manage Map Suite projects and issues in Jira. ThinkGeo Jira also has Curtus View projects on it, and this guide only cares about Map Suite Projects and issues.

This section introduces how the Map Suite projects are organized.

After signing in ThinkGeo JIRA, goto Projects/View all projects and you will see all the projects and categories.

Project types:

• Project types / Software All the projects are under this group.
• 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. )

• Map Suite Products: Map Suite products line, including iOS, Android, GIS Server etc.
• ThinkGeo Internal Projects: The internal projects, like single point, demo etc.
• Professional Services: The professional projects, like CV projects.

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 Project.

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.

Everyone has the permission to create an issue, do please create it within the correct project.

• Issue Type:
  • Task: Task that needs to be done
  • Bug: Problem that impairs 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
  • Epic: Large piece of work that encompasses many. We don't need to have it for most cases.

(Story kind of overlaps with Task/Bug/Improvement. Story is more from user's perspective but Task/Bug/Improvement is from developer's perspective.)

• 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 leave it unassigned.

Then click Create button and the task is created.

A JIRA workflow is the set of statuses and transitions that an issue goes through during its life cycle.

Backlog is where the initial task should be. We could put any idea in this column. It is like a bucket, you can throw anything you think it is worth to do.

• Backlog→TODO: Begin to work on this issue;
• Backlog→Closed: Meaningless issue, no need to work;

TODO is a filtered tasks we decide to work with. Your team leader decides what tasks should be in this column.

• TODO→In Progress: Working on this issue;
• TODO→Closed: Duplicated issue or some reason;
• Re Open→In Progress: Rework on this issue;

In Progress holds all the tasks that are in progress. Technically, one guy must have only one task in this column. You cannot work on two issues at the same time right? If yes, please re-consider if the task is created proper.

• In Progress→Closed: Not worth to do;
• In Progress→In Review: Developer finished the issue

Once your task is complete from In Progress column, it is not mean this task is done. In another word, you need to ask your leader or the task assigner to review and verify if this is what he wants. In this step, your task will have two directions to go.

• In Review→Resolved: Resolved this issue, if it satisfies the task assigner, they will drag the task from this column to Resolved column.
• In Review→Closed: Something like a workaround, but no good solution right now;
• In Review→Re Open: Review failed,If it is not fine, not fully complete, or there might be some other options to check, they will drag it back to Re Open.

• Resolved: The issue has been resolved;

• Closed→Backlog: Redo this issue.

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.

1. Navigate to the Backlog of your desired board.
2. Click the issue that you want to set the Original Estimate for.
3. In the Issue Detail View, type your estimate in the Estimate field.

Once you have started to work on a specific issue, you need to log your work by following these steps:

1. Select the issue you want to log time on.
2. Go to More > Log Work.
3. Fill in the following Log Work fields, and select Log.

As we are going to use JIRA for all the issues, we must follow this workflow when using JIRA.