Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-22640

Filter by fix version release date


    • 90
    • 40
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update: 23rd December 2015

      Hi all,

      Thanks for participating in this issue, either by voting, commented or just watching. We highly value your feedback in all forms, and through suggestions in jira.atlassian.com is not different. We use this channel often to learn the best we can with how customers use JIRA and how we can continue to improve the experience for as many users as possible.

      We have revisited this issue again recently and wanted to reiterate that there are still currently no plans to implement this suggestion, and it is not currently on any JIRA team’s roadmap at this stage. That said, there are several add-ons on the marketplace which should solve some customers' use-cases for this suggestion.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Kerrod Williams
      Kerrod (dot) Williams (at) atlassian (dot) com
      Product Manager, JIRA

      On the Issues Search page, there are fields for filtering by Created, Updated, Due, and Resolved dates. It would be extremely useful if I could filter by the Fix Version release date.

      Each Version in a JIRA project has an optional Release Date field. If that release date is set, I'd like to be able to filter on it. So, like the Updated Date fields in Issues Search allows for explicit or relative date values, I'd like to be able to create a query based on a Fix Version's release date.

      So instead of saying "Updated After" below, it would say "Fix Version Release Date After" or something.

      Our developers work on multiple projects that each have their own version release dates. I would like to create a filter for my developers where it shows all issues that have a Fix Version release date between now and 1 month in the future.


      Below are possible alternatives.

      Third-party apps

      There are some third-party apps in our Marketplace that offer more specific functions to perform JQL searches:

      Those might provide the function that you need.

      In case you have doubts about their features I strongly suggest reaching out to their vendor support (check the Support tab).

      You can also start a 30 days free trial of third-party apps in case you want to test them.

      Workaround using Automation for Jira

      I was able to achieve a similar behaviour by performing a workaround using Automation for Jira (which is built-in) to populate a custom date picker field with the date of release on issues associated to the fix version being released.

      • Create a custom field of the type date:
      • Now let's create the Automation rule
      • Use the Version released trigger:
      • Use a Issues fixed in version branch:
      • Use the action Edit issue, selecting the custom date picker that was created and applying the smart value below:

        Here's a recording showing how that rule works, and also showing that you can use that field as a criteria on searches: Release date search test.mp4

      For existing issues

      In order to update the existing issues, you will need to perform some manual work.

      • You can search for issues that have a fixversion set but don't have a release date set yet and then export them to CSV:
      • Edit the CSV file leaving only the necessary columns. The dates you will set will be the ones corresponding to the release associated to each issue, which you can check on the project's Release section:
        • The date format in the CSV file will depend on the current settings of your Jira instance
      • You can then import the file back into your instance trough the external system import at https://<YOUR_SITE>.atlassian.net/secure/admin/ExternalImport1.jspa
        • Make sure to perform the correct mappings
      • The issues will be updated with the values set in the CSV file
        • That update changes the issue updated date as well

            Unassigned Unassigned
            34eae6e385ec erockx
            416 Vote for this issue
            184 Start watching this issue