Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Project Amendments for Jira project

Prasad Andrews
Contributor
August 8, 2019

1) Need functionality where in an EPIC should reflect start date and End date from it’s linked stories (i.e. the earliest start of any story becomes start date of EPIC and oldest of stories becomes an End Date).


2) EPIC to show consolidated time spent recorded in it’s linked issue items, for example, if an EPIC has 4 stories and there are some hours logged in these 4 stories then those should roll up to EPIC.


3) If anyone creates a story within an EPIC then few fields should to be mapped automatically such as “Added by Department” and “Scrum team”

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 9, 2019

Hello Prasad,

I hope you're having a nice Friday!

The goals you are looking for can not be achieved using only JIRA, although we have some feature requests opened to achieve those goals:

Sum story points or hour estimates for any epic links

Post Function to copy fields from Epic to Story

However, there are some plugins that could provide with those functionalities, like Epic Sum Up - Light and Automation for Jira - Server Lite.

Using those add-ons, you could use the following rules to achieve your need:

1 - The Start and End dates of any issues (Including Epic) are always configured when the issue is created and solved. That being said, you need to ensure that the first child issue is created together with the related Epic and that the Epic will only be closed when the last child issue is closed to. You can follow the documentation below to achieve this:

Automation of the week: How to transition an epic when all stories are done

2 - The Epic sum-up App will properly sum your stories estimation to the Epic

3 - This Automation rule should work for you:

Screen Shot 2019-08-09 at 18.37.14.png

P.S: I used the Assignee and Component fields in the example above because I don't have the “Added by Department” and “Scrum team” fields, however, the rule above works just fine for custom fields too.

Additionally, feel free to vote and watch the feature requests provided to increase its priority and also receive notifications about any updates.

Let me know if this information helps.

Prasad Andrews
Contributor
August 21, 2019

@Petter Gonçalves Automation for lite we are using the trial version. For the trial version am unable to achieve if:matches options.

Suggest an answer

Log in or Sign up to answer