I need to write an automation rule based on the user who logged the work. I have Tempo Timesheets enabled on my Jira software cloud.
I am calling the Tempo REST APIs https://api.tempo.io/core/3/worklogs/issue/{{issue.key}} which returns all work logs on this issue.
I need the latest author from the response. So I thought I can get that information if I can call Jira REST APIs like https://<my Jira cloud URL>/rest/api/2/user/accountId={{webResponse.body.results.author.first.accountId)}}
Then I realized the accountId is a list and I am not sure how to get only the latest worklog entry from the {{webResponse}} and the respective accountId to pass it to Jira REST API.
Is there a way to get the user who triggered the worklog from Tempo or Jira REST APIs?
Thanks
Hi Philip,
Did you perhaps input the wikimarkup header "h1." in the comment section while on the new JIRA issue view? If so, the tag won't be rendered on the frontend automaticly as the new viewer doesn't recognise the format:
<p>h1. I have manually added this heading</p>
<h1><a name="Ihavemanuallyaddedthisheading"></a>I have manually added this heading</h1>
Do let me know if this is not the case. Hope you can elaborate on the steps.
Cheers, Syauqi
Yea this is the exact case. Is there a reason why the new view does not recognise the wiki format ?
Cheers, Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As mentioned here New Atlassian Editor, we'll eventually phase out the wiki markup on future editor in favour of universal markdown syntax.
Here's the example formating shortcuts that you can use for the new editor:
Hope this explains.
Cheers, Syauqi
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.
No worries Philip. Happy to help :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Syauqi I just wanted to double check something. You mentioned that Jira will eventually deprecate the "custom" wiki in favour of a universal markdown syntax.
My first question is will this change also apply to Jira server as well as cloud.
Also is there a place to look out for updates on when this will happen along with other development updates?
Cheers, Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the question Philip, there haven't been any progress for the suggestion nor re-introducing archived markdown Jira labs plugin. If you are interested on the capability, please do keep an eye out and leave a feedback on this active thread for any changes and updates: Markdown for JIRA Add-On compatibility. Though, there's no guarentee that the feature will be implemented or any ETA that I could provide to you.
If you have any other questions, please let us know and we'll be happy to help.
Thanks again for your feedback!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If wiki markup will not be supported, what happens to the almost 3,000 Jira issues my Org has created over 3 1/2 years using Wiki markup? We refer back to them as a form of documentation, but it sounds like alot of formatting will end up getting scrambled.
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.