Is there a way to set-up forms to use a naming convention for the summary (it seems only free field.

Question

hi all,

Is there a possibility to enforce a naming convention for the summary when using Forms in Jira Cloud?
the first part of the to be created issue is part of the epic name it is linked to:

epic name= xxxx - yyyy

issue name should be: xxxx - zzzz

We use Forms to help people, who don't work regurarly in jira, to quickly create an issue.
Thanks for your help!

Manoj Kumar Gangwar · Accepted Answer

Hi @barbara foblets, yes, it's possible, but not directly with Jira Forms alone. The best approach depends on how strictly you want to enforce the naming convention.

I would suggest using Jira automation for this.

Gabriela - LeanZero · Accepted Answer

Hi Barbara,

Yeah, Forms on their own won't enforce the summary format - the summary stays a free-text field no matter what. But you've got two nice ways to get there, depending on whether you'd rather have the summary built for people or have Jira reject the ones that don't fit.

The one I'd reach for first, since your form users don't live in Jira: let automation assemble the summary so nobody has to remember the pattern. A rule that triggers on "Issue created", then an Edit issue action that sets the Summary. If your epic is named "xxxx - yyyy" and you want new issues to come out as "xxxx - zzzz", you pull the "xxxx" part off the epic and stick the typed bit after it - something like:

{{issue.parent.summary.split(" - ").get(0)}} - {{triggerIssue.summary}}

The .get(0) grabs the first chunk before the " - " (use {{issue.epic.summary}} instead of parent if you're on the older Epic Link), and the second half is just whatever field your form drops the short bit into. One heads-up: right at creation the epic value sometimes comes back empty, so if that happens just pop a "Re-fetch issue data" action in before the Edit and it behaves. Add a condition on project or issue type so it only fires where you want - and the person filling the form just types the short part while Jira builds the full summary for them.

There's a nice older thread doing basically this (pushing the epic name into child summaries) if you want a worked example: https://community.atlassian.com/t5/Jira-Software-questions/Adding-the-name-of-Epic-into-Sub-tasks-Summaries/qaq-p/1765698

Now, if you actually want to block the issues that don't match rather than quietly fix them for people, that's a validator on the create transition - the native ones only do presence/regex, so folks usually reach for ScriptRunner or JMWE to run a regex check there. I should probably admit this next one's my own app - I work on CogniRunner over at LeanZero, which does that kind of validation in plain English instead of regex, so "the summary has to start with the epic's prefix" is just a sentence you write. Leaving it here in case the validation route's ever the one you want: https://marketplace.atlassian.com/apps/298437877/cognirunner . But honestly, for what you're describing I'd start with the automation-builds-it approach first - it's the least for your form folks to think about.

Hope that helps! what