Can a Story under an Epic inherit fields?

[Barry Scallan]

Simple and Expected use case is 

When creating a Story under an Epic, inherit field from the Epic for the created Story

Steps

With Epic - Create Issue Type - Story

Workflow post function implemented

Copy Value From Other Field (JSU)

• Issue Relation: issue in transition to issue in epic

• Copy Field Fix versions to: Fix versions
• Run as user: JSU Add-On User

Have tried also: Issue Relation: issue in transition to epic

There is no error reported

Is inheritance supported for Epic>Story?

[Nicolas Tagle · Accepted solution]

Hello Barry,

This is archivable using automation, This is an example:

Hope this help you out, let us know how it goes. Cheers,

Nico.

[Barry Scallan]

Hi Nicolas,

This look very promising!

Correct me if I'm wrong please, this works off the Current Issue on screen. 

Is there a way to use the direct Epic link or Parent for it because it would work while creating Stories in the Epic screen, what if I create a story while having a sub task or bug or another story on screen?

Found below

[Nicolas Tagle]

I think the that options are included but I currently can't check.

[Barry Scallan]

No problem Nicolas, this is the solution I needed.

Thanks very much for your help!

[Charlie Misonne]

Where did you put the JSU post function? On the create step of the Story workflow right?

Is the fix version field on the edit screen for Stories?

[Barry Scallan]

Hi Charlie,

Thanks for the message. I placed the post function on the Create Issue transition. The screens Create Story (Create operation), View Story (view operation) and Edit Story (edit operation) have the fixVersion field.  It should work as it is implemented as it's quite straightforward.

This is an attempted workaround I'm having to implement because what I had implemented : a Create Issue transition - open a Screen to allow users enter the fields required by a fields required validator. This won't work for Stories, but works for Bugs no problem.