scriptRunner changing field summary

Alex
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 18, 2022

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 ?

 

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 18, 2022

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?

Alex
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 18, 2022
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 18, 2022

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.

Alex
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 19, 2022

@Nic Brough -Adaptavist-  I can't find a solution

Alex
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 19, 2022

@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" ?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 20, 2022

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.

Suggest an answer

Log in or Sign up to answer