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
Next: Root
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.
Hi,
If I will use Automation rules, it will be possible to auto fill the summary field for a request on Jira Service Managament?
If is possible how i should handle?
Thank you
Yes, and no. The summary has to be set when the issue is created, and automation runs after that happens. So what you could do is set a default summary, and then have an automation that triggers on issue create that edits the summary to something else.
Well, for a summary i wrote a default summary : eg. Select <user>. Where is "user", with automation rule i would like to select whatever assignee.
So on the automation rule how i should do to aapear maybe a list with the name of the users and pick the one/ones i needed?
Eg: Select <users> to be replaced with Select Cristina.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One way of doing it is to use replace, like this:
{{issue.summary.replace("<user>","{{issue.reporter.displayName}}")}}
Another option would be to use substringBefore.
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.
What about if i want to select a user?
It is useful this information {{issue.summary.replace("<user>",{{issue.reporter.displayName}}")}} but if want to select a user? To be different that one who reported? A mentioned user or something like that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's possible too, the reporter was just an example. For example, I have an automation that looks for a specific text within the description that is then used to find duplicate issues. You could also use a custom field to specify the user, either a user picker one or a text field.
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.