You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello, this is my first time on JIRA Community, we are trying to use Power Automate to edit a JIRA issue, however, when we are passing values in fields text field, we are getting errors, attaching screenshots:
This is the flow body that we are using, we are trying to update summary field.
This is the error that we are getting:
we want to know how should we pass the field/update parameters values, so that it should get updated for the respective ticket ID.
@Hari Narayn Thank you. Do you know if there is a way to add an attachment through the JIRA edit issue operation as well?
Yes, there are MS PA actions for getting SP list items and using that data to update Jira fields. I have multiple MS PA flows that do this.
You need to have a Premium Power Automate license for the user that creates/runs the flow.
Is there any way to update the status via JSON using the JIRA edit feature? I know status is not quite the same as something like priority and assignee.
Yes, I do believe that it is possible and I am doing something similar with some other custom fields, and in our Jira environment the issue status is a custom field. You will just have to do some digging to make sure that you get the correct field/JSON.
Here is an example of the JSON that I am using to do multiple updates to a single issue at once:
That's a good call, I definitely will need to keep custom fields in mind for the future. We don't store our issue's status as a custom field though, we just store it in the status. From what I've seen so far, I think I'm supposed to do something with the transition ID, but I just haven't been able to figure it out yet.
That is a good point in return. I have also used PowerShell to update the status of issues and in that case, you are correct that it was an issue transition that needed to be done for it to work properly.
If you want to go down that "rabbit hole", I used the JiraPS PowerShell module and the PS command is Invoke-JiraIssueTransition -Issue IssueID -Transition TransitionID
No need to go down the rabbit hole, I think. The transition ID is provided in the Power Automate for the "Edit Issue". Look at OPs 5th field in the picture.
@Michael Bruno Hi Michael. I'm facing the same issue at upadting the a ticket status
I've filled the transition ID field with the value of the transition I see in my flow
I tried with and without brackets but I still receive the same error. Moreover I don't know If I need to fill more fields. There's no documentation at all. I thank you in advance, Pas
Sorry, but I have no better information than you do. I have tried just about every method I can think of for formatting the TransitionId and I haven't been successful getting it to change. Without access to the underlying API or better documentation I have no clue on how to make it work. It does seem a field is required to use this Automate action though, so if you are going to keep trying, I would recommend putting in a field value that just changes a field to the value it already is (i.e., change existing priority medium to priority medium).
I would suggest reaching out to Microsoft support on this. The last time I reached out they didn't seem super knowledgeable with the JIRA connectors though, just warning you if you want to try that.
You can always try a custom connector option too, but I understand that would be really annoying, especially with the need to hide your API token (probably via key vault/secret server, at least that is getting a lot easier to do). The ability to do it without hiding the token was the main reason we wanted to use this built-in connector, but without better documentation or clarity on the underlying API call your options are pretty limited. If you're trying to make more advanced calls than just creating an issue or changing an assignee you might have to bite the bullet on doing the call through a custom connector.
If you go the custom connector route and you use Azure Key Vault (AKV), you can use the premium actions for AKV to pull in your API token if you store it in AKV.