What plug in will allow me to pre-fill custom fields for an issue created from the epic screen

[Randell Pelak]

We have a custom field called feature.  It is required.  When on the view epic screen for a specific epic, we like to add issues to the epic using the + in the child issues section.  But it always pops up the create issue screen and forces us to choose the feature, which is the same as the epic's feature 99.999% of the time.

Since this is jira, the answer is always a plugin.  Is there a plugin that will pre-populate that feature field on the create issue screen that comes up with the value of the same field in the epic from which we used the + in the child issues section? 

[John Funk]

Hi Randell,

The only plugin I am aware of that might do this is the ScriptRunner Behaviours app. But it doesn’t work for all custom fields yet.

The other thing is if it is really that frequently that the value is the same, why not go ahead and populate it as a post function in the workflow or use an automation rule?

[Randell Pelak]

yeah, can't post populate since it is a required field.  And while it is almost always the same as the epic.  There are exceptions.

I did find a post about scriptrunner saying it couldn't do it on jira cloud, which I forgot to mention is what we are on.

[Hannes Obweger - JXL for Jira]

Hi @Randell Pelak

my team and I work on an app that might not be exactly what you have in mind, but perhaps worth giving a shot: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a range of advanced features, including support for (configurable) issue hierarchies, issue grouping by any issue field(s), and inline issue creation.

These features are, of course, all integrated; e.g., the inline issue creation considers the hierarchy and issue grouping at the place where you want to create the issue. So if you would group the issues within an epic by their Feature field, and then create an issue in the respective group, the Feature field will be pre-filled, like so: 

I should clarify that this doesn't actually use the epic's Feature field, so you'd need at least one child issue with the correct Feature value set in order to "establish" the group.

Any questions just let me know,

Best,

Hannes