nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Release Date not populating

Jagriti

I have created a JQL to pull through a list of all items in a release , for next three releases

"project = "IT-Ops Team" AND fixVersion in ("1st Infra Slot - May | 11/5/19", "1st Infra Slot - June | 15/6/19", "1st Infra Slot - July |13/7/19") AND issuetype in (Epic, Task, Story)"

The data which gets pulled is correct , however , the "Release Date" column in always blank, the fix version is not pulling the release date .All fix versions have been created with release date .

How can I solve this issue to display appropriate "release date" for each fix version, please assist .

Thanks

Accepted answers

All comments

Tarun Sapra

Hello @Jagriti

Currently it's not possible to display release date in the issue navigator view or to use it in JQL.

I think in your instances there is already a custom field which has been created by the admins called "Release date" and hence the confusion because you are thinking of this field as the one which should give you the date of the release of the fixVersion.

Please see this open ticket by using JQL with release date

https://jira.atlassian.com/browse/JRASERVER-22640

And the ticket for having release date in the issue navigator view in Jira has been set to "Wont do" by Atlassian.

https://jira.atlassian.com/browse/JRASERVER-10788

Jagriti

Hi Tarun

thanks for the quick response .

I have a gadget on the dashboard "Filter results gadget" which uses the JQL i have mentioned above, on this gadget i have myself added the field "release date" as the management wants a view like that .

Is there any way the fix version can fetch its associated release date . May be a different jql etc.

Jagriti

or may a another gadget from the market place?

Nic Brough -Adaptavist-

Yes, adding a custom field to the issues, but not actually putting anything in it will give you an empty display.

I would throw that field away and replace it with a "scripted field" - Scriptrunner (I name this first because I work with the authors, and have used it for a lot longer than joining them, so I am most familiar with it) and other scripting or automation apps can do this.

A scripted field can read the release date off the appropriate version and display it on the issue for reporting. You will need to put some extra thought into it - an issue can have many fix versions, your code will need to read them all and decide which is most appropriate if it finds more than one.