• 19
    • 16
    • 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.

      Atlassian Update - 23 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap. 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.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      Currently you can look for an issue that has been updated in the last 5 days. It would be useful to tie this in with the working days set in Time Tracking to search for issues created in the last 5 working days.

            [JRASERVER-22506] JQL search with working days range

            b59dfb12ba9c whatever issue they might have, they had 15 years to fix it since this issue was reported. Things like this, and the overall terrible UX of most of their products, convinced me over the years that there are some bigger fundamental issues within Atlassian. Most of us here are devs, and we all have the feeling that this feature could be implemented as a quick win, yet it does not happen. dmeyer could you please tell us what we are missing, so we could understand why the reluctance to do this? With honestly is usually the best way to manage expectations.

            Diego Verbrugghe added a comment - b59dfb12ba9c whatever issue they might have, they had 15 years to fix it since this issue was reported. Things like this, and the overall terrible UX of most of their products, convinced me over the years that there are some bigger fundamental issues within Atlassian. Most of us here are devs, and we all have the feeling that this feature could be implemented as a quick win, yet it does not happen. dmeyer could you please tell us what we are missing, so we could understand why the reluctance to do this? With honestly is usually the best way to manage expectations.

            Ian Brown added a comment -

            I'm thinking now that there's some fundamental design issue within the Jira storage system that stops Atlassian from doing this. 

            This seems such a simple request that there has to be a reason it's not been resolved. Or am I being too kind?

             

            Ian Brown added a comment - I'm thinking now that there's some fundamental design issue within the Jira storage system that stops Atlassian from doing this.  This seems such a simple request that there has to be a reason it's not been resolved. Or am I being too kind?  

            Amir H added a comment -

            It's been open for more than 10 years! please address this issue,

            Amir H added a comment - It's been open for more than 10 years! please address this issue,

            IMO a team day out should affect performance stats. That way you can see the impact that the team day out has on your performance.

            Greg Hoggarth added a comment - IMO a team day out should affect performance stats. That way you can see the impact that the team day out has on your performance.

            Ian Brown added a comment -

            It would also be great to have an equivalent of Excel's NetWorkDays function - so we can also filter out public holidays, and have a custom filter of non-working days.

            That would allow us to filter out days when the team wasn't available for work. e.g. if retro, demo and planning were all on the same day and took all day, it's not time we'd expect to count against queue time for work. Another example is that if we had a team day out, then we wouldn't want to affect performance stats. 

             

             

            Ian Brown added a comment - It would also be great to have an equivalent of Excel's NetWorkDays function - so we can also filter out public holidays, and have a custom filter of non-working days. That would allow us to filter out days when the team wasn't available for work. e.g. if retro, demo and planning were all on the same day and took all day, it's not time we'd expect to count against queue time for work. Another example is that if we had a team day out, then we wouldn't want to affect performance stats.     

            Would be very useful having this, we keep track of how long it's been since a ticket update in the Service Desk project due to SLAs, but since the SLAs pause over the weekend filtering by not updated within so many days doesn't work for us, always end up with stuff being updated on the Friday but then showing up in the 'No Update' list on the Monday

            Alex Bromilow added a comment - Would be very useful having this, we keep track of how long it's been since a ticket update in the Service Desk project due to SLAs, but since the SLAs pause over the weekend filtering by not updated within so many days doesn't work for us, always end up with stuff being updated on the Friday but then showing up in the 'No Update' list on the Monday

            I recently discovered business days functions in automation and they were very useful!

            Like I was setting up issue due date to now.plusBusinessDays(2) 

            We need same capability in JQL! So many ppl asking the community how to filter something for X business days. Consider them to be votes!

            Alexey Paveliev added a comment - I recently discovered business days functions in automation and they were very useful! Like I was setting up issue due date to  now.plusBusinessDays(2)   We need same capability in JQL! So many ppl asking the community how to filter something for X business days. Consider them to be votes!

            up +1 vote

            Steven Villanueva added a comment - up +1 vote

            Jozsef Lehocz added a comment - - edited

            Today is Friday. The JQL

            createdDate >= startOfDay(-4d) ORDER BY created ASC

            returns 182 issues, but the JQL code suggested previously

            createdDate >= startOfDay() OR
             (createdDate >= startOfDay("-1d") AND createdDate < startOfDay() AND createdDate >= startOfWeek("+1d") AND createdDate < startOfWeek("+4d")) OR
             (createdDate >= startOfWeek("-2d") AND createdDate < startOfWeek("-1d") AND createdDate >= startOfDay("-3d") AND createdDate < startOfDay("-2d"))

            returns only 8 issues, which have been created today. So this does not seems to work for me.

            Jozsef Lehocz added a comment - - edited Today is Friday. The JQL createdDate >= startOfDay(-4d) ORDER BY created ASC returns 182 issues, but the JQL code suggested previously createdDate >= startOfDay() OR (createdDate >= startOfDay( "-1d" ) AND createdDate < startOfDay() AND createdDate >= startOfWeek( "+1d" ) AND createdDate < startOfWeek( "+4d" )) OR (createdDate >= startOfWeek( "-2d" ) AND createdDate < startOfWeek( "-1d" ) AND createdDate >= startOfDay( "-3d" ) AND createdDate < startOfDay( "-2d" )) returns only  8 issues, which have been created today. So this does not seems to work for me.

            Peter Walker added a comment - - edited

            This may work for some people:

             

            createdDate >= startOfDay() OR
            (createdDate >= startOfDay("-1d") AND createdDate < startOfDay() AND createdDate >= startOfWeek("+1d") AND createdDate < startOfWeek("+4d")) OR
            (createdDate >= startOfWeek("-2d") AND createdDate < startOfWeek("-1d") AND createdDate >= startOfDay("-3d") AND createdDate < startOfDay("-2d"))

            Peter Walker added a comment - - edited This may work for some people:   createdDate >= startOfDay() OR (createdDate >= startOfDay("-1d") AND createdDate < startOfDay() AND createdDate >= startOfWeek("+1d") AND createdDate < startOfWeek("+4d")) OR (createdDate >= startOfWeek("-2d") AND createdDate < startOfWeek("-1d") AND createdDate >= startOfDay("-3d") AND createdDate < startOfDay("-2d"))

              Unassigned Unassigned
              clepetit ChrisA
              Votes:
              562 Vote for this issue
              Watchers:
              227 Start watching this issue

                Created:
                Updated: