Jira Workflows

Flow : Analysis/Development

Context

Analysis/Development project in JIRA should be used to add tasks, analysis documents and ask questions.

Diagram

Open (Create Issue)

Steps

#

Page

Description

1

Select your support Project
Select the Issue Type

2

Complete required informations
Choose the right Priority

Default Assignee is the Project Lead.
Give a complete Description of the case
- How To Reproduce (HTR) step by step is really efficient
Click CREATE > An email will be sent to all subscribers (participants in the issue)
- The issue can be Edit after creation.

3

Attach Files or Attach screenshot to show the context of the issue.

Issue Statuses

* All actions sent email to subscribers (participants on an issue).

Statuses

#

Status

Transitions (Next steps)

1

The issue is open and ready for the assignee to start work on it.

>> Open Transition screen >> Resolved

>> In Progress

>> Open Transition screen >> Closed

2

This issue is being actively worked on at the moment by the assignee.

>> Fixed Locally

>> In QA Review

>> Open Transition screen >> Resolved in TEST

>> Open Transition screen >> Resolved in PROD

>> Open

3

Issue is fixed in the local machine of the developer and is ready to be deployed.

>> In QA Review

>> Open Transition screen >> Resolved in TEST

>> Open Transition screen >> Reopened

4

The issue is being verified by the eVision QA specialist.

Theses buttons are only available for eVision.

>> Open Transition screen >> Resolved in TEST

>> >> Open Transition screen >> Reopened (Returns to development step)

4

Issue was deployed in the TEST environment (or PRE-PROD/STAGING environnement if the client has their own environnement for QA). The client needs to transition the issue if it is confirmed to work after testing.

>> Open Transition screen >> Push to PROD

>> Open Transition screen >> Reopened

>> Open Transition screen >> Closed

5

Issue has been validated by the client in the TEST environment (or PRE-PROD/STAGING environnement) and is ready to be pushed to PROD environment.

>> Open Transition screen >> Resolved in PROD

>> Open Transition screen >> Reopened

>> Open Transition screen >> Closed

6

The issue has been deployed in the PROD environment. The client needs to close the issue if it is resolved after testing.

>> Open Transition screen >> Reopened

>> Open Transition screen >> Closed

7

A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

>> Open Transition screen >> Reopened

>> Open Transition screen >> Closed

8

This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.

>> In Progress

>> Open Transition screen >> Resolved

9

The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

>> Reopened

Transitions Screens

#	Screen	Description
1		Resolution screen should be updated with the Resolution of the issue
2		Push (deploy) to the next environment
3		Reopen screen allows to reopen a fixed issue to add new comment or if it is not fixed as required.
4		Close screen allows to close the issue.

Flow : Support (SLA) - Maintenance

Context

Support project in JIRA should be used only to report cases according to the SLA (generally related to the PRODUCTION environment). Other cases should be report in analysis/development project.

Diagram

Open Support Case (Create Issue)

Steps

#

Page

Description

1

Select your support Project
Select the Issue Type

2

Complete required informations
Choose the right Priority

By selecting the Component, the system assigns to the right eVision resource.
Give a complete Description of the case
- How To Reproduce (HTR) step by step is really efficient
In the Environment field, add all informations where the issue can be tested, such as :
- Production
- Account
- Application #
- Browser and version
Click CREATE > An email will be sent to all subscribers (participants in the issue)
- The issue can be Edit after creation.

3

Attach Files or Attach screenshot to show the context of the issue.

Issue Support Statuses

* All actions sent email to subscribers (participants on an issue).

Statuses

#

Status

Transitions (Next steps)

1

The issue is open and ready for the assignee to start work on it.

>> In Progress

>> Open Transition screen >> Closed

2

This issue is being actively worked on at the moment by the assignee.

>> Fixed Locally

>> Open Transition screen >> Resolved in TEST

>> Open Transition screen >> Resolved in PROD

>> Open

3

Issue is fixed in the local machine of the developer and is ready to be deployed.

>> Open Transition screen >> Resolved in TEST

>> Open Transition screen >> Reopened

4

Issue was deployed in the TEST environment (or PRE-PROD/STAGING environnement if the client has their own environnement for QA). The client needs to transition the issue if it is confirmed to work after testing.

>> Open Transition screen >> Push to PROD

>> Open Transition screen >> Reopened

>> Open Transition screen >> Closed

5

Issue has been validated by the client in the TEST environment (or PRE-PROD/STAGING environnement) and is ready to be pushed to PROD environment.

>> Open Transition screen >> Resolved in PROD

>> Open Transition screen >> Reopened

6

The issue has been deployed in the PROD environment. The client needs to close the issue if it is resolved after testing.

>> Open Transition screen >> Reopened

>> Open Transition screen >> Closed

7

This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.

>> In Progress

8

The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

>> Reopened

Transitions Screens

#	Screen	Description
1		Resolution screen should be updated with the Resolution of the issue
2		Push (deploy) to the next environment
3		Reopen screen allows to reopen a fixed issue to add new comment or if it is not fixed as required.
4		Close screen allows to close the issue.