I have checked the community already and found some entries on the same issue.
It seems an easy setup:
The "Edit issue" function let's you add a json under "additional fields" without selecting something using the drop down. Here we use:
However the request participant filled won´t be field with anything - without any errors so I am not sure where to start troubleshooting (FYI I have no experience with JSON so just adapted the information from other issues and made sure to close all brakets )
btw at absolut best the user should be something within smart value! However need to know format used in case you suggest something ;)
Hi @felix_weber ,
The way you are doing it looks good. A smart value wont work imo as you want to "add" and not just "set"
As your audit log doesn't show any errors, the structure of your JSON should be correct (otherwise it would complain about the wrong format or a non-valid JSON)
If this is a real world example tho, could you try adding it using the email-address of the user? Within Cloud I tend to see that users are only properly resolved when the userid is used (and that would be the email address)
On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link. We've seen a number of questions already asking for...
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