Forums

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

print historical unique list of all due dates with strikethrough on all but the current due date

Rajal Shah
Contributor
April 3, 2025

I have JIRA on cloud version. In the JIRA structure, I would like to write a formula that publishes all the historical values of the due date field  with all strikethrough against all of them except the current due date value.

 

I write this formula for it, but it failes in the "$ ->" row. Any suggestions?

 

 

WITH myArray = history.changes.filter($.field = "duedate") :

WITH previousDueDatesArrays = WITHOUT (myArray, LAST(myArray)) :


IF(IS_EMPTY(myArray), "",
JOIN(
WITH(
myArray,
$ ->
IF(
$ == LAST(myArray),
$,
concat("~~",$, "~~") + ", "
)
),
""
)
)

3 answers

2 accepted

Suggest an answer

Log in or Sign up to answer
3 votes
Answer accepted
Tuncay Senturk
Community Champion
April 5, 2025

Would this work?

WITH myArray = history.changes.filter($.field = "duedate") :
WITH previousDueDatesArray = WITHOUT(myArray, LAST(myArray)) :
WITH formattedArray = MAP(myArray,
IF(
$.to = LAST(myArray).to,
$.to,
CONCAT("~~", $.to, "~~")
)
) :
JOIN(formattedArray, ", ")

 

Rajal Shah
Contributor
April 6, 2025

great.. This worked (see values on the right edge of the screenshot! I had to map history to a array value of Due Date from the variable selection at the bottom.. Is there something I can do to make your history.changes... formula work instead?

 

Also, I could not understand how the ".to" fixed the code? Any explanation on that would be awesome. Thank you @Tuncay Senturk 

Screenshot 2025-04-06 at 6.22.48 PM.png

Like Tuncay Senturk likes this
Tuncay Senturk
Community Champion
April 7, 2025

Whe you pick a specific field like Due date, Structure gives you a simplified array of history changes only for that field. So you don't need to filter for duedate, you're already only getting duedate changes.That's why history works directly as myArray = history.UNIQUE()

 

For your question regarding the ".to",

you're working with objects like this: { "from": "2025-03-17", "to": "2025-03-24" }

if you had just done MAP(myArray, ...) without .to, you'd be trying to compare the entire object, not just the date string. So, you need $.to because that's the new value of the due date in the change history record.

Like Stepan Kholodov _Tempo_ likes this
Tuncay Senturk
Community Champion
April 7, 2025

Last but not least, I'm glad it worked :) 

Rajal Shah
Contributor
April 7, 2025

@Tuncay Senturk - can you tell me why the history function did not work out of the box for me? It gave me a formula error.. I had to map it to use field through the UI.. but curious what is missing in my setup to not have the history function work for me. Thanks.

1 vote
Answer accepted
Yuliia_Borivets__SaaSJet_
Atlassian Partner
April 4, 2025

Hi @Rajal Shah 

I don't know how to do that with a formula, but if you are open to using apps, you can try the one from my team. It's called Issue History for Jira, and you can create a report with changes in the due date for each issue in your project.

Report example:

due dates sorted by issue key.png

Rajal Shah
Contributor
April 4, 2025
 
I need this to work in the Jira structure. It should be a straight-forward formula so purchasing something would be difficult to go through procurement anyways..
Thank you for taking the time to respond 
0 votes
Petru Simion _Simitech Ltd__
Atlassian Partner
April 6, 2025

Hi @Rajal Shah ,

 

If you will not be able to find your solution of the shelf and if you will get approval to use apps you can try Issue History Dashboard for Jira , an app released by our company.

You can easily restrict your search by Field Updated = Due Date and Date of Change from and to as you wish.

 

Regards, 

 

Petru

Screenshot from 2025-04-06 20-34-08.png

TAGS
AUG Leaders

Atlassian Community Events