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.
Hello, tell me please:
When the ticket is escalated to another project, the name should automatically (in the other project) change to: SUMMARY - "issuing access"
How can this be done in ScriptRUNNER ?
What do you mean by "escalated to another project"? Please tell me you're using "create linked issue" and not moving the issue as part of a standard process?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, good, but that's a cloned issue - the clone process will have filled in a summary already. Have you removed it from the display in that screenshot to hide the content? (It's fine to do that, but it looks like it's blank, rather than obscured).
Assuming that is the case, then would it be fair to say the need is
When a new issue is cloned from an existing one (not moved, you are doing that later), you want to change the summary of the new issue?
If so, then you need a "listener" that can detect the clone event, work out the new issue from it and set a new summary. That should be quite simple, you might even find a script at https://library.adaptavist.com that does something similar.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- I can't find a solution
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- It is necessary that (summary), regardless of the original name of the task, when escalated to another project (clone), always had (in the clone project) the name "task for you" ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would not recommend doing that. Destroying the summary of an issue by overwriting it with "task for you" isn't helpful. "Task for you" is completely redundant, the person already knows it's for them because they are the assignee, and you'll have destroyed the quick and easy to see summary of what you're asking them to do.
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.