Auto-populate summary field with value of customized field

[Deleted user]

Hi,

I would like to auto-populate the summary field with a value of a customized field in the create issue screen. When creating an issue there is a custom drop down field which is required. The value of the drop down field should then appear in the summary field.

1. Custom field "Meeting type" includes "Value#1"
2. Summary should show "value#1"  of chosen value of field "Meeting type"

The purpose is that the user doesn't have to fill in the summery as it will be auto-populated

Any ideas?

Many thanks! BR,

Alex

[Austin Neuner]

I am testing out the post function method on a transition. In my test, I want a custom field "Abstract" to copy the value from "Summary" and then for "Summary" to copy the value of "Description". Here are my inputs.

       Summary = Summary

       Description = Description

       Abstract is left empty

When I transition the issue, here are the outputs I get:

       Summary = Optional[Description]

       Description = Description

       Abstract = Summary

Is there a way to eliminate the "Optional[]"? I already tried changing the field configuration to require the Description, but that did not change the output. Any suggestions?

[Deleted user]

@Nic Brough [Adaptavist], thank you for your answer. I will try it with the post-function first.

[Mark Gancsos]

Hi there, did you ever solve this? We have basically the same goal that you did.

[Deleted user]

Sorry for my late reply. I solved it with the Jira Suite Utilities Plugin. Within a transition screen the user is forced to enter text into a custom field. The JSU postfunction (e.g. from parent to sub-tasks) prepends the value of the custom field to the summary.

[Nic Brough -Adaptavist-]

You'll need to inject some clever javascript to do that - stuff that can react to the changes in your fields as the users click and update, and dynamically set the summary.  It will also need to disable their entry into the summary field.  I think you can do it with Behaviours from the "Script Runner" add-on.

Another option is to do it after the create, which is easier to script for as a post-function will receive what the user finally settled on, there's no need for dynamic activity capture, but it does mean destroying what the user enters in the summary because they have to enter one to get that far.  When I've done it this way in the past, I've added a custom field for what the user puts in as the summary and populated that with their input, so nothing is lost.

However, no-one really seems to like generated summaries as they tend not to be as useful as freely chosen text.