Forums

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

how to set the value of Epic Due Date with now plus the sum of time remaining of all child tickets

Kent Chiu
Contributor
October 11, 2023

Hi,

I have difficulties setting the Epic's Due Date in Jira Cloud automation with the value of now plus the Epic's time remaining.

I tried to use the following syntax but they do not work:

{{now.plusDays({{issue.fields.timeestimate}}})}}

or

{{#=}} ({{now}} + {{issue.fields.timeestimate}})

 

That statement is within the For: Epic (parent) section:

Epic due date.png

What is the correct syntax to set the Epic Due Date with the current time (i.e. now) plus the Epic Time Remaining (i.e. SUM of the time remaining from the child tickets)?

 

Thank you for your help.

Regards,

Kent

1 answer

1 accepted

2 votes
Answer accepted
Gundlupet Sreenidhi
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 21, 2018

@Michał Kitowski,

In short: 

A Story is for requirements

A Defect/ Bug is for defects identified that needs to be fixed.

A Test is for recording the different steps that are to be followed in order to test a Story or Defect. There are multiple other issue types that may be necessary for Defect Management which you will decide based on your organizations Test Management Process.

All are used for completely different purposes. You may try to use Stories to record your tests, but this is not very efficient and not recommended. There are multiple Test Management plugins you can use for JIRA (Xray, Zephyr, etc..)

 

Test Management is a process in itself that has tremendous benefits and should not be considered as a part of Defect Management or Backlog management. 

We ourselves use XRay for Test Management - you can get details here.

You can also have a look at Zephyr as an alternative.

Michał Kitowski
October 22, 2018

Thank you Gundlupet,

Lets then assume that team cannot use other tool than Jira for test issue. Would you then recommend to add "Test Issue" type or use something already there in Jira choice?

 

Regards,

Michal

Gundlupet Sreenidhi
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 22, 2018

If you are unable to use any add-on / tool, then Yes - you should track all test cases using its own issue type. This helps with maintainability and reporting.

However I highly recommend using one of the Test Management process available in the market. Many of them are already supported in the Atlassian Marketplace.

https://marketplace.atlassian.com/search?query=test%20management

Note: You will still be working within JIRA for most of them - you need not go to a different tool for test management.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events