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,455,287
Community Members
 
Community Events
175
Community Groups

Assignee in SD projects - how to consider workload when everything is assigned internally

Edited

Hi,

We're a consulting company with 180+ consultants/developers using Jira SW for most of our customers (+600 users). They each have +1 projects where they report change requests, service requests and incidents. For most of our customers, Jira SW works best, but we now have a few new customers where we see the absolute need for Jira SD, mostly for the sake of SLA reporting. 

To monitor workload, reporting and to get a picture of issues per consultants, team etc, we're using the assignee and assignee group throughout the whole organization, i.e "if you're assigned to an issue, it's your responsibility and your move".

As I understand, this is impossible with Jira SD as the customer cannot be an assignee. I understand we're suppose to use statuses, but as our workflows have 10-15% statuses that is on the customer's side, and this will make the reporting a bit tedious. 

Example of consultant statuses (change req):

- Open, in design, in development, code review, ready for deployment + +

Example of customer statuses:

- Waiting for customer, In QA, awaiting estimate approval, awaiting deployment approval + +

I know we could re-assign the issue to a dummy user when the issue is at the customer side, but as far as I know, there's no way to then assign it back to the "last consultant"..

Any suggestion on how not to re-arrange all our reporting and ways of working?

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events