Who change these statuses? developer or Tester?

majid hussain March 31, 2016

This question is in reference to Atlassian Documentation: What is Workflow

There are statuses New, Open, In Progress, Resolved and Closed or Reopen

I expect the following flow

  1. New or Open by Tester
  2. Developer changes to In Progress when start developing
  3. When fix, developer changes status to Resolved and assign to tester
  4. Tester verify the issue and closed it or Reopen it. 

Please confirm

 

1 answer

0 votes
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 31, 2016

There are no norms but this is a good way to do it. And, frankly, 1 can be done by anyone and 4 should be available to tester and the reporter (even if the reporter is not a tester).

I usually like open workflow but you can use project roles and restrict transitions to those roles. Up to you!

majid hussain March 31, 2016

Thanks Jobin for quick reply
I want to following this workflow. I am tester and my team developer insist step3 and step4 would be done by Tester/QA but my opinion is step3,4 would be done by developer please confirm


1. Add New Jira (By tester or developer)
2. Open(when defect confirmed by PM) or ON Hold (Under discussion)
3. In Progress (developer started work)
4. Resolved (developer completed his work and assigned to tester/QA)
5. Reopen (Issue did not fix by Tester/QA)
6. Closed (issue fix by tester /QA)

Thanks

Majid

 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 31, 2016

We can't really tell you how to implement your own processes.  What you're writing out here is a good definition of a workflow which sounds like it will work well for you.  You should go ahead and build the workflow like that and try it out with your users!

Suggest an answer

Log in or Sign up to answer