Is there a way to auto-fill the story field?

[光野 かおる]

Hi Jira Community,

Our team uses the restriction function to ensure that all required information is filled in before closing issues. Because of this, we are required to complete all fields in both stories and subtasks.

However, most of the time, stories don't contain much information and mainly serve as a container for subtasks.  And it takes time to fill in the story fields everytime.

So, is there any way to automatically populate the story field with default information?

[Tomislav Tobijas]

Hi @光野　かおる ,

On top of what Gor said, have you thought about separating workflows for Stories and Sub-tasks? It depends on how you've set up those restrictions, but it might also be relatively easy just to make a copy of the workflow you currently have, remove those restrictions on the newly created one, and assign it to Story work type 🤔

Cheers,
Tobi

[Gor Greyan]

Hi @光野　かおる

If the fields for the Story, is static every time, or you know, in which condition which value should field contain, you can use automation.

Here’s how:

1. Go to Project settings → Automation → Create rule.

2. Select the Trigger: “Issue created.”

3. Add a Condition: Issue Type = Story.

4. Add another condition, if needed.

5. Add an Action: “Edit issue fields.”

6. Specify which fields to update (e.g., Description, Priority, Environment, etc.) and enter your desired default text or values.

If you provide more information, I can help to reach this.

[Sascha H_]

Hi @光野　かおる ,

your question implies three things:

1. Story and Sub-tasks are using the same screens, thus the same fields.

2. Story and Sub-tasks are using the same workflow.

3. The mandatoriness(restriction) checks are workflow based, not field configuration.

I recommend not going down the road of duplicating data between parent and child tickets, because that brings a lot of async tears. How, when and what direction ought data to be synced later on?

Breaking stories into bits is common, but then Sub-tasks ought to describe what part of the whole they are addressing.

Definitly you do need to provide two workflows in order to lift mandatoriness requirements where unnecessary, as @Tomislav Tobijas describes.

In addition, you could provide different screens for stories and sub-tasks, in order to provide fields as required on each level.

In case it doesn't get clear: My answer is challenging your definition of the work split between Story and Sub-tasks. 

Finally i realize my answer is focused on company managed projects. So, I hope you are not using team managed here.

Cheerio,

Sascha