Degraded performance Customers may experience issues using Community search. Our team is investigating.
The new agent base license model actually hurts us as a potential customer, if I understand the model correctly.
Is anybody who wants to edit or transition a SD ticket automatically an Agent?
I would have considered the guys who create the tickets to be Agents and after that JIRA users from Analysis, Dev and Test take over. According to Atlassian everybody who touches the SD ticket needs to be an Agent.
Is that correct?
For us that would mean a 100+ Agent license vs a 25 Agent license to avoid using comments to request that Agents transition a SD ticket. It just seems strange to me.
This is correct Seb
Without another plugin only agents can work with the issues.
Customer can transition issues via the Service Pack for Service Desk Plugin.
Another way would be the "cloning" of an issue for working in a second or third level.
An service desk issue comes in your queue and you see it's a task for your dev team.
If a service desk issue is confirmed it's created in your DEV project and linked to the SD - issue. (Create on Transition Plugin)
After this you can sync these issues with Field Sync Plugin.
(Second way you can even sync comments - but every synced comment is going public to the customer)
Here the links to check this.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
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