We are using JIRA Service Desk for our customer support whereas our development team works on JIRA. So when the support team needs help from development team, they create a Linked Issue in JIRA. So in JIRA you are two categories of incidents:
1. Incidents created as linked incident from the JIRA service desk (external or customer incidents)
2. Incidents, which are directly created in the JIRA itself by our internal stakeholders like QA, Product Management etc. (internal incidents)
We need to some how identify that whether incident is external or internal, which is required as JIRA Service Desk incidents are SLA bound and hence should get higher priority and also reporting has to be different for both the types.
Can someone please suggest how can we do so?
One easy way is of course to create two projects in JIRA, one for external incident and the other one for internal incident. But this will disturb the way dev. team works as they need to work on multiple projects. We do not want that way.
Do let me know in case I need to provide any further details ?
One way of solving the problem is to make use of the groups linked to the reporter.
Support team users can be linked to group "Service Desk Agent"
Developers can be linked to group "Developer"
The JIRA automation lite add on can be used to update priority (lite version is free):
How to setup add on:
Reporting can make use of:
reporter in membersOf("Developer*")
* the applicable group
Thanks for your reply. Unfortunately, this add-on is only available for service version and not for cloud. We are using cloud version (both for JIRA and JIRA Service Desk).
Not sure if JIRA has some way to create automation rule like it is there for JIRA service desk. I will contact my JIRA admin and try to explore it.
Thanks again. Service desk automation can only change the status of incident in JIRA Service Desk (though it can be based on the transition of an issue from JIRA core). But I have not found a way to change/set something in JIRA based on JIRA service desk. The logic you mentioned earlier would have surely work but JIRA service desk automation cannot change/update JIRA ticket or at least I have not found a way to do so. If you (or someone) knows how to do that, I will be grateful.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs