Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,049
Community Members
 
Community Events
176
Community Groups

How to know the current ticket of a developer ?

I want to know the current ticket a developer is working on. We have a lot of statuses in JIRA right, so people tend to not select the particular status while doing the development.

I want to know if we have any automation or APIs to have only one ticket in the "Dev in progress" status for one developer. They cannot have multiple tickets under this status. This will be easy for me to track the current tickets they are working on.

 

Thanks in advance.

2 answers

Hey @Akash Lenin 

There is no real way to do that. You can see similar question answered here https://community.atlassian.com/t5/Jira-Software-questions/Only-one-active-issue-per-user/qaq-p/1506258

If you don't mind me sharing my thought - trying to make JIRA allow only one issue per user in a given status is trying to solve the symptom, not the problem. I speak from experience here :)

What is the reason people don't use right statuses? Maybe there are too many, or they do not understand the process? Or maybe the team spirit is low and "no-one cares"? 

0 votes

Welcome to the Atlassian Community!

You can do some automation to try to prevent people having more than one issue in a status, but its complexity will be proportional to the complexity of your workflows, and a much better option is to simply allow people to do it, report on "assignee = X and status = Y" regularly, and then get your human processes fixed and people educated as to how they should be working (and ideally, simplify your workflows to make it easier for them to get it right)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events