Theoretically Jira automation can be used instead of Jira webhooks, but you will need to send the expected request with custom data (the format of the request data should look like one in the comment above)
I checked the statusCategory in a browser and the following returns:
{"self":"https://jira.jcrew.com/rest/api/2/status/14149","description":"","iconUrl":"https://jira.jcrew.com/","name":"Selected for Development","id":"14149","statusCategory":{"self":"https://jira.jcrew.com/rest/api/2/statuscategory/2","id":2,"key":"new","colorName":"default","name":"To Do"}}
So it does show the correct status (Selected for Development) but the defaults to this at the end of the line: "colorName":"default","name":"To Do"}}. Thoughts? If you can help me fix this, I think it will be my last question! :)
Oh, I see...so you are using different names for Status and Status Category in your Jira Configuration. In that case you need to adjust the card data. Please edit your workflow, open the last step and edit the schema for adaptive card - you need to change
toUpper(body('Parse_JSON')['issue']['fields']['status']['statusCategory']['name']) to
> Also, with the old connector recognized links. Is there anyway to make links active in this one?
Eric, could you please add more details on this issue? not really sure what is "old connector" and what is "this one"...Do you mean if we can somehow reuse the webhooks from Jira Server connector (that is deprecated now) and use them in new flows?
I have reached out to Atlassian and am awaiting help. Didn't realize this was the same issue as it is not happening in my original workflow which is working the same with reference to the same jira project.
As for the the reference to "old connector", I was speaking of the format of the deprecated connector's results vs. the new format. In the first image from the now deprecated connector, links added into jira comments were displayed in teams as rich text links. While in the 2nd image, the are not. Not the end of the world, but the user was inquiring. Thanks.
The Jira markup will not be displayed on new Adaptive cards as they are using different rules, that is why formatted text from Jira event is displayed as is. Old cards (Office 365 cards) from Jira Server connector were using the same rules for displaying formatted text...So that is expected behavior
As for the error on your flow with conditions it seems that this channel and/or team are using different access rules. Have you tried to install Workflow app to that team directly (<Team> -> Manage Team -> Apps -> <Add Workflows app> OR find Workflows app and select Add to a team) ?
Thanks for answering my question on the jira markup. Unfortunate, but I think that the users will be happy to have this rather than nothing. As of the error, I attempted to create the workflow directly from the teams channel itself with no luck. Though I think that I have figured out that the issue is related to the permissions of the actual teams channel. When I create a new channel, everything works as expected. With that said, I now have to determine how to modify the permissions of existing channels that want this configure again.
One more question (I know I've said that before, but I think this time will be true!) Here it goes. Is there a way to change the font size for each of the pieces? See image.
Atlassian Team members are employees working across the company in a wide variety of roles.
September 24, 2024 edited
Hi all,
It seems like Jira webhooks schema was changed a bit and avatar urls for user is not always received. If you have an error like below while trying to execute the workflow, please update the adaptive card schema by one mentioned in this article (updated card).
65 comments