I would like to be able to add issues from Jira Service Desk directly to my Jira Software..
I'm using the Cloud version in both cases.
At the moment the only way I can figure out how to do it is to create
a new Jira Software issue for each Jira Service Desk issue and then link them...
I'm wondering if anyone has a better way to do this...
I'm finding it hard to stay on top of the 2 cross-connected issues.
One option is to use Automation and have it create the issue for you in JSW, you can either do it when the issue is created in Jira Service Desk or when it reaches a certain status, have a specific field value etc.
is the Automation you speak of home grown or is it an App that ties into JIRA?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Automation for Jira is an app that Atlassian bought earlier this year and they have started to roll it out to cloud customers this week, see this thread.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
do all the complaints about the # of rules/ global rules in that last thread bother you?
I have no clue how many rules I'd be using,
but It sounds like I'd need to use the global rules to get an issue from Service Desk to Software...
Being pretty uninformed, I have no clue what that means for me, but I do know I can't afford the JIRA premium tier.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It was at the beginning before they changed the limits, but Atlassian really listened to the concerns and changed the limits. Here is a FAQ that they created. My company is a former Automation customer and we rely heavily on it and have close to 20,000 executions in a 30 day period, so we will most likely stay on premium. But I will work on getting the number of executions down, some of them are to broad and can be configured in a different way.
But in you case if you decide to create an issue in JSW when it's created in JSD is excluded from the limits as it is a cross product action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks for your great inputs!
I'll look further into this Automation as a solution
I'm also waiting to see if anyone else has some other ways of dealing with this...
I'm pretty weak on this whole Agile software thing to start with :)
I always find myself adding a tasks to JSW after I actually complete them (but before I check the changes in) because of the way my ADHD mind works when I'm in the code fixing things... I was hoping to protect myself from myself, but its not quite working :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
funny, I commented yesterday and said that this answered my question, but somehow it didn't get submitted...
My comment was that this was way eaiser to setup than I imagined it would be...
Thanks again for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.