Adding fields for transition screens, that are not part of the ticket?

[Benjamin Peikes]

We are using transitions as operations, for instance, to replace the "Create Linked Ticket" which is only available on Service Desk. During the transition, we would like to be able to collect information that will be used in the script handling the transition (we use script runner), but it's not a field that should ever be used on the ticket itself.

Example:

We are creating our own "Create linked ticket" transition, and would like to have the user set the assignee on the new ticket. The way we're trying to do it now,

1. Create a new field, called "LinkedTicketAssignee" for the project
2. Add the new field to the project, and to the screen associated in the transition
3. Have the script grab the value in the screen, and use it to create the new linked ticket
4. Clear the value of "LinkedTicketAssignee" in the original ticket

This is definitely not ideal, because LinkedTicketAssignee has nothing to do with the original ticket, particularly if the transition is used to create multiple linked tickets.

Is there any way to create "transition only" fields?

[Ilya Turov]

Tbh I don't see why it's not ideal and why that field "has nothing to do with the original ticket", since it's definitely takes a part in it's lifecycle.

Also, since you are already clearing it's value after processing it you are not littering your db with unnecessary data.

But, if you really think you need some "transition only" fields, I believe power actions plugin can add "fake" fields on transition screens.

e: tho looks like it's not available for cloud