I am using a JIRA macro on an on-prem Confluence 6.14.2 page.
In the macro, as part of the JIRA issue filter, I want to use the currently logged-on Confluence user as a variable in the JIRA assignee field. Then, I'll restrict editing of the page so that users cannot see any issues that are assigned to others. Users can only see their own issues, at least in Confluence. (!Important)
Here is my xhtml:
<ac:structured-macro ac:macro-id="39265a4e-f7e7-4c75-b8c2-c956cde9922c" ac:name="jira" ac:schema-version="1">
<ac:parameter ac:name="jqlQuery">project = PROJECT AND status != Done AND assignee = [current Confluence user] </ac:parameter>
That is the exact variable that I was trying, and for some reason it stopped working this week. I had it working last week, but this week instead of using the currentUser() variable string, the JIRA macro resolved the variable string to my logon id string -- essentially hard-typing it into place for all users of the page.
Now today, inexplicably, it is indeed working again. What is going on with the currentUser() variable that sometimes works and sometimes does not?!!
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events