• 11
    • 16
    • Hide
      Atlassian Update – 17 May 2019

      Hi everyone,

      Thank you for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. 

      After careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, some of them including your highly voted suggestions. Also, in the recent Jira Server releases we have shipped some highly-voted features and improvements. 

      We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

      To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 17 May 2019 Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.  After careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, some of them including your highly voted suggestions. Also, in the recent Jira Server releases we have shipped some highly-voted features and improvements.  We hope that you appreciate our candid and transparent communication. You can learn more about our  approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing  Recently resolved issues  and  Current work and future plans . Kind regards, Jira Server Product Management
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      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.

      Example:
      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.

            [JRASERVER-22640] Filter by fix version release date

            Zacchaeus Widner added a comment - - edited

            For specific dates you can use the following:

            fixVersion in releaseDate("on yyyy-mm-dd") 
            Example: fixVersion in releaseDate("on 2022-10-07")

            you can also use a date range with specific dates

            fixVersion in releaseDate("after yyyy-mm-dd") AND fixVersion in releaseDate("before yyyy-mm-dd") 

            Example:fixVersion in releaseDate("after 2021-10-01") AND fixVersion in releaseDate("before 2022-09-30") 

            Zacchaeus Widner added a comment - - edited For specific dates you can use the following: fixVersion in releaseDate("on yyyy-mm-dd")  Example: fixVersion in releaseDate("on 2022-10-07") you can also use a date range with specific dates fixVersion in releaseDate("after yyyy-mm-dd") AND fixVersion in releaseDate("before yyyy-mm-dd")  Example:fixVersion in releaseDate("after 2021-10-01") AND fixVersion in releaseDate("before 2022-09-30") 

            Don Hamp added a comment -

            There appears to be no way to search and return the 3-4 fields tied to a release.   Releases cannot be treated as an issue type?  For example give me all stories and end date  where end date is the release date for that fix version for the story. 

            Don Hamp added a comment - There appears to be no way to search and return the 3-4 fields tied to a release.   Releases cannot be treated as an issue type?  For example give me all stories and end date  where end date is the release date for that fix version for the story. 

            Lily Wang added a comment -

            any update for this issue ? how to filter those issues whose fix version shall be released in 3 days ?

            Lily Wang added a comment - any update for this issue ? how to filter those issues whose fix version shall be released in 3 days ?

            I've been asked to provide releases by quarter for approximately 50 projects. Since there is a Release 'report' available on every project, this should be no problem, right?  

            Problems:

            There is only gadget that will add releases to a dashboard, "Custom Content".

            With the number of projects and releases that exist, it takes a while for the dashboard to render, so that it's nearly not useable. 

            Solution 1 on us: ask projects to archive old releases to improve performance.  The Atlassian documentation indicates that when a project is archived, the issues will not show up in searches, so that's a no-go; however, the issues DO show up in searches. Is this intended or not? If intended, that's great, please update the documentation. 

            Solution 2 on Atlassian or 3rd party: create a gadget that will allow us to add releases within a certain timeframe (usually by quarter) including release dates.

            Solution 3 on Atlassian: Include filter options to list releases and release dates like issues

            deborah duffy added a comment - I've been asked to provide releases by quarter for approximately 50 projects. Since there is a Release 'report' available on every project, this should be no problem, right?   Problems: There is only gadget that will add releases to a dashboard, "Custom Content". With the number of projects and releases that exist, it takes a while for the dashboard to render, so that it's nearly not useable.  Solution 1 on us : ask projects to archive old releases to improve performance.  The Atlassian documentation indicates that when a project is archived, the issues will not show up in searches, so that's a no-go; however, the issues DO show up in searches. Is this intended or not? If intended, that's great, please update the documentation.   Solution 2 on Atlassian or 3rd party: create a gadget that will allow us to add releases within a certain timeframe (usually by quarter) including release dates. Solution 3 on Atlassian: Include filter options to list releases and release dates like issues

            Filter by fix version release date for people who found an error after downloading this ZIP Add a neat map like this: https://static.rust-lang.org/dist/rust-1.17.0-nightly.tar.gz Or this: https://static.rust-lang.org/dist/rust-1.17.0-nightly.zip Check the size, if you're using a different release date from http://thatpainter.com/.

            Michael Barnes added a comment - Filter by fix version release date for people who found an error after downloading this ZIP Add a neat map like this: https://static.rust-lang.org/dist/rust-1.17.0-nightly.tar.gz Or this: https://static.rust-lang.org/dist/rust-1.17.0-nightly.zip Check the size, if you're using a different release date from http://thatpainter.com/ .

            This is very important, I need this!

            Deleted Account (Inactive) added a comment - This is very important, I need this!

            Hi everyone,

            Thank you for your interest in this issue.

            While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. 

            After careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, some of them including your highly voted suggestions. Also, in the recent Jira Server releases we have shipped some highly-voted features and improvements. 

            We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Kind regards,
            Jira Server Product Management

            Gosia Kowalska added a comment - Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future.  After careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, some of them including your highly voted suggestions. Also, in the recent Jira Server releases we have shipped some highly-voted features and improvements.  We hope that you appreciate our candid and transparent communication. You can learn more about our  approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing  Recently resolved issues  and  Current work and future plans . Kind regards, Jira Server Product Management

            Thank you for the answer, we will follow up on this topic.

             

            BR,

            Jerome

            Jerome Thuillier added a comment - Thank you for the answer, we will follow up on this topic.   BR, Jerome

            We are on an old version of Jira v7.2.1 and using the following script:

            package com.onresolve.jira.groovy.test.scriptfields.scripts
            
            import com.atlassian.jira.component.ComponentAccessor
            import com.atlassian.jira.issue.comparator.VersionComparator
            import com.atlassian.jira.project.version.Version
            
            def versionManager = ComponentAccessor.getVersionManager()
            def versions = versionManager.getVersions(issue.projectObject)
            def lowestFixVersion = issue.fixVersions.findAll({v -> !v.released}).min({Version a, Version b -> a.releaseDate <=> b.releaseDate})
            def releaseDate = lowestFixVersion?.releaseDate
            return releaseDate

            We've been having some problems with sorting on this field, it no longer appears to work properly. And it may not work at all on other version of Jira.

            So hopefully Atlassian will implement sorting by Release date properly within core Jira!

            Brett Vasconcellos added a comment - We are on an old version of Jira v7.2.1 and using the following script: package com.onresolve.jira.groovy.test.scriptfields.scripts import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.comparator.VersionComparator import com.atlassian.jira.project.version.Version def versionManager = ComponentAccessor.getVersionManager() def versions = versionManager.getVersions(issue.projectObject) def lowestFixVersion = issue.fixVersions.findAll({v -> !v.released}).min({Version a, Version b -> a.releaseDate <=> b.releaseDate}) def releaseDate = lowestFixVersion?.releaseDate return releaseDate We've been having some problems with sorting on this field, it no longer appears to work properly. And it may not work at all on other version of Jira. So hopefully Atlassian will implement sorting by Release date properly within core Jira!

            @brett.vasconcellos I got a script parser error for a.ReleaseDate and b.ReleaseDate

            no such property for class: Java.lang.Object.

            Should i need to add other incudes ?

            Jerome Thuillier added a comment - @brett.vasconcellos I got a script parser error for a.ReleaseDate and b.ReleaseDate no such property for class: Java.lang.Object. Should i need to add other incudes ?

              Unassigned Unassigned
              34eae6e385ec erockx
              Votes:
              448 Vote for this issue
              Watchers:
              191 Start watching this issue

                Created:
                Updated: