Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

How to track issues resolved by DEvelopers

Malavi Lester
Malavi Lester
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
December 22, 2023

Normally, after the develeopment the stories or issues are tested by QA and moved to Done, In this case, QA will be the assignee while closure.

 

how do i track the no of stories or tasks a developer as worked on

Answer
Watch
Like Be the first to like this
256 views

2 answers

1 vote
Aron Gombas _Midori_
Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
December 22, 2023

If I correctly understand your workflow, then you change the assignee of an issue when it moves from "development" to "testing" from its "developer value" to its "tester value".

If I were you, maybe it wouldn't do it, but use the "Assignee" field to store the developer and add an additional "User picker" type custom field with the name "Tester". That way "Assignee" would not change, and maybe tracking/reporting is more flexible and precise.

But if you want to keep your current workflow, then you could try to use JQL to collect the historical information. More precise, use the WAS operator on the Assignee field! 

Reply
0 votes
Sayed Bares [ServiceRocket]
Sayed Bares [ServiceRocket]
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
December 22, 2023

@Malavi Lester welcome to the Atlassian community!

I believe Pie Chart Report addresses your use case. However, can you elaborate further? are developer and QA 2 different personas here? initially, it will be assigned to a developer and then to QA?

Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events