Skip to main content

Moving Issue through workflow

After creating issue you can move it througt project's workflow. Workflow is determined by Project settings. In most cases we will use basic datastat workflow

img.jpg

To Backlog​

Issues that are stored in backlog are usually the issues which will be taken care of later throught the project or are not relevant in this stage of the project

You can use back log to store tasks which you don't want to forget.

From Backlog to Open​

When you decide that task is relevant for the project and must not be forgoten in next months you can put it in Open status. Open status is displayed on Kanban boards in most of the projects.

From Open to InProgress​

After deciding that you or programmers will work on task you can move it from Open status to InProgress status. When you do this, you have to add/edit data inside the issue.

Edit data in issue after moving from Open

When you move the task from Open to InProgress usually you will have to add:

  1. Assignee
  2. Priority
  3. Epic link
  4. Labels
Automation

This transition can be done with automation if Branch name equals Jira Issue Key. For more information on this automation find Here

From InProgress to ForMerge or ForTesting or Testing​

When issue is done by programmers they request pull request on GitHub (which transitions task automatically to ForMerge) or put it into status ForTesting / Testing.

ForTesting

Process:

ToDo->InProgress->ForTesting->Testing->Done

All programmed tasks are primarly put into ForTesting status. From this status team or project leader MUST communicate which tasks in ForTesting status will be tested and move them to Testing status.

This way the testing team or progreammer knows exactly which issues have to be tested when doing testing for the next version release.

This is important step if you have testing team outside of your programming team. When moving the issue from InProgress to ForTestning status, it will automatically remove "Assignee" field and

Automation

When moving from statuses Open, ToDo, Discussion, Backlog to status ForTesting it will run automation rules which:

  • removes assignee
  • Add a comment to task "(username) moved task to ForTesting"
    img.jpg

When Requesting Pull Request on GitHub, if the Branch has the same name as Jira Issue Key then issue is automatically transitioned to ForMerge status. See more information Here

Testing

Process:

ToDo->InProgress->Testing->Done

Issues can be put directly to Testing status if programmer is testing the issue himself or if issue was forgot to move to Testing or it was communicated to add it into Testing later during testing phase

When moving it into Testing or ForTesting status usually you have to edit:

Edit data in issue after moving in from InProgress
  1. Add changelog (write what was changed/fixed/added,...)
  2. Remove/Change Assignee (new assignee will be added then by testing teams or project leaders)

If you project allows you you can even edit Development and Create branch or Create commit and connect task with GitHub

From ForMerge to ForTesting​

This transition has to be made as soon as Jira Task is done by programmmers and merged to develop so it can be tested.

If Branch on GitHub has the same name as Jira Issue Key issue will be automatically transitioned to ForTesting once it will be merged to develop or production enviroment. For more information click Here

From Testing to Done​

After the issue is tested it can be moved to Done status. After that programmers can release new version of program.