Uploaded image for project: 'Jira Work Management Cloud'
  1. Jira Work Management Cloud
  2. JWMCLOUD-19

Ability to configure Business board to show issues for more than 14 days and remove issues before 14 days

    • 407
    • 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.

      +underlined text+

      Atlassian Update – 6 May 2024

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use Jira so we can continue improving your experience. To uphold our value for transparency, we wanted to provide an update that we have no immediate plans to put this suggestion on our near term 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, however, this problem remains on our radar and we will provide further updates if our stance changes. Please don't hesitate to contact me if you have any questions.

      Regards,
      Eric Zheng
      ezheng@atlassian.com
      Product Manager, Jira

      Problem Definition

      Case 1:
      For leading tracking (a use case specifically support by JIRA), having items on the board for more than 14 days is extremely common. In some cases, this can easily be up to 6 months.

      Case 2:
      A customer has too many issues in his "Done" column and wants to remove them before the 14 days term

      Case 3:
      A customer has multiple columns tied to statuses that are configured to Done category.

      Suggested Solution

      1. Make it possible to configure a Business board to show issues for more than 14 days.
      2. Make it possible to remove issues from a Business board before the 14 days term.

      Workaround

      This is by no means a fix but I hope it will help you get quicker access to those Done issues that are more than 2 weeks old:

      1. Write a JQL query that returns all issues in a project that have been done for more than 14 days e.g. 
        project = CJSWK AND (fixVersion in unreleasedVersions() OR fixVersion is EMPTY) AND status = Done AND NOT (updated >= -2w OR statusCategory != Done) ORDER BY Rank ASC
        
      2. Run that JQL and copy the URL of the search page
      3. Create a shortcut that links to that URL. I called mine Older Done Issues:

        1. screenshot-1.png
          screenshot-1.png
          178 kB
        2. screenshot-2.png
          screenshot-2.png
          350 kB

            [JWMCLOUD-19] Ability to configure Business board to show issues for more than 14 days and remove issues before 14 days

            sguio added a comment -

            Hi all,

            Thank you for your patience. I'm pleased to let you know that we have now updated Removed resolved items after with the options of 7,14,30 and 60 days.

             

            Regards,

            Susana Guio

            Engineering Manager, Jira

            sguio added a comment - Hi all, Thank you for your patience. I'm pleased to let you know that we have now updated Removed resolved items after with the options of 7,14,30 and 60 days.   Regards, Susana Guio Engineering Manager, Jira

            Dan C added a comment -

            +1 for this, seems like a pretty simple feature we should have 

            Dan C added a comment - +1 for this, seems like a pretty simple feature we should have 

            Yeah, we really need this as a feature at our company. We always have issues on our boards that need to stay longer than 14 days for an internal review. I hope this is implemented soon. Thanks! 

            Lukas Mahoney added a comment - Yeah, we really need this as a feature at our company. We always have issues on our boards that need to stay longer than 14 days for an internal review. I hope this is implemented soon. Thanks! 

            +1 for this. It is confusing for users when issues disappear from the board unexpectedly.

            Maybe the best option would be to match what already is provided on the "List" tab, a Hide Done Items option

            Robert Eiser added a comment - +1 for this. It is confusing for users when issues disappear from the board unexpectedly. Maybe the best option would be to match what already is provided on the "List" tab, a Hide Done Items option

            We need this as a company too, make a button for letting the done tickets stay in that phase for infinity

            Johan van Zaanen added a comment - We need this as a company too, make a button for letting the done tickets stay in that phase for infinity

            Our team needs this.

            it is a lot easier to manage the tickets from the board.

            Thanks.

            Ikhsan Habibi added a comment - Our team needs this. it is a lot easier to manage the tickets from the board. Thanks.

            Our team needs this

            Brooke Alarie added a comment - Our team needs this

            Another way I've found to find the >2w Done items was to click on the LIST tab ... brings up all items in the project, and then filter on DONE items.  Not perfect but simple way to quickly find those "missing" done items.

             

            Darran Wilkinson added a comment - Another way I've found to find the >2w Done items was to click on the LIST tab ... brings up all items in the project, and then filter on DONE items.  Not perfect but simple way to quickly find those "missing" done items.  

            Please make this feature available. It doesn't make any sense only to offer this option to Company managed projects.

            Mariana Zanchetta added a comment - Please make this feature available. It doesn't make any sense only to offer this option to Company managed projects.

            +1 please.

            Mike Donnarumma added a comment - +1 please.

            Konrad added a comment -

            Hi, why is it so hard to add this feature an let the user decide when to hide the issue from board view??

            This is very frustrating.

            Konrad added a comment - Hi, why is it so hard to add this feature an let the user decide when to hide the issue from board view?? This is very frustrating.

            We need this soon...

            Ajay Hemanth added a comment - We need this soon...

            Definitely a needed feature.

            Roman Pietrzak added a comment - Definitely a needed feature.

            Melo Jorge added a comment -

            Our team needs this.

            its a lot easier to manage the tickets from the board

            Thanks

            Melo Jorge added a comment - Our team needs this. its a lot easier to manage the tickets from the board Thanks

            Our team needs this.

            David Drong-Reisch added a comment - Our team needs this.

            Our team needs this.

            Thomas Shepherd added a comment - Our team needs this.

            Our team needs this

            Volodymyr Swift added a comment - Our team needs this

            We need this  .... come on its basic functionality

            Darran Wilkinson added a comment - We need this  .... come on its basic functionality

            Our team needs this

            Karina Karomaro added a comment - Our team needs this

            Our team needs this.

            Natalia Nami added a comment - Our team needs this.

            Our team needs this{}

            Aleksandr Oper added a comment - Our team needs this { }

            Our team needs this

            Renata Adora added a comment - Our team needs this

            Our team needs this

            Anastasiia Sheveriova added a comment - Our team needs this

            Our team definitely needs this 
             
             

            Juli Kryvytska added a comment - Our team definitely needs this     

            Our team needs this.

            Ira Pumpkin added a comment - Our team needs this.

            Our team needs this!

            Anzhelika Meif added a comment - Our team needs this!

            Our team needs this!

            Kateryna Gemini added a comment - Our team needs this!

            Our team needs this

             

            Karolina Exodus added a comment - Our team needs this  

            Our team needs this 😓. Please

            Cesar Ramos added a comment - Our team needs this 😓. Please

            Our team needs this{}

            Dariia Fenix added a comment - Our team needs this { }

            Our team needs this

            Nadiia Millori added a comment - Our team needs this

            Our team definitely needs this

            Valm Part Time added a comment - Our team definitely needs this

            ALSHAIKH added a comment -

            Our team needs this

            ALSHAIKH added a comment - Our team needs this

            Our team needs this

            Diana Bertha added a comment - Our team needs this

            Valery added a comment -

            Our team needs this.

            Valery added a comment - Our team needs this.

            Our team needs this

            Aleksandra Szczesna added a comment - Our team needs this

            Our team needs this 😓

            Mykyta Resolve added a comment - Our team needs this 😓

            Our team needs this

            Anna Gellar added a comment - Our team needs this

            Our team needs this

            Yuliia Silentium added a comment - Our team needs this

            Our team needs this!

            George Atlas added a comment - Our team needs this!

            Igor Lex added a comment -

            Our team needs this

            Igor Lex added a comment - Our team needs this

            Our team needs this

            Dmytro Zacky added a comment - Our team needs this

            Our team needs this

            Taras Gonzalezz added a comment - Our team needs this

            Our team ABSOLUTLY needs this

            Dana Atance Lozano added a comment - Our team ABSOLUTLY needs this

            Arina Lana added a comment -

            Our team needs this
             
             

            Arina Lana added a comment - Our team needs this    

            Our team needs this

            Dmitriy Bing added a comment - Our team needs this

            Our team needs this

            Daria Bambi added a comment - Our team needs this

            Our team needs this

            Roman Sidewinder added a comment - Our team needs this

            Igor Tenet added a comment -

            Our team needs this

            Igor Tenet added a comment - Our team needs this

            Our team needs this

            Egor Makuhin added a comment - Our team needs this

            Our team needs this

            Ira Chelsea added a comment - Our team needs this

            Our team needs this

            Vitalina Vitaminka added a comment - Our team needs this

            Our team needs this

            Dmitriy Omelianenko added a comment - Our team needs this

            Our team needs this. We have more than 3k issues (maximum board limit) in our JSM project, so as a result not all issues are displayed at native board and this is a problem. Of course, we have did a workaround with creating separate Jira Software boards to work on them, but it is very uncomfortable for us.

             

            We need a possibility to reduce "X" days, when issues are still displaying in final statutes (Done) at our JSM board to get back work on native JSM board.

            Aleksandr 2easy added a comment - Our team needs this. We have more than 3k issues (maximum board limit) in our JSM project, so as a result not all issues are displayed at native board and this is a problem. Of course, we have did a workaround with creating separate Jira Software boards to work on them, but it is very uncomfortable for us.   We need a possibility to reduce "X" days, when issues are still displaying in final statutes (Done) at our JSM board to get back work on native JSM board.

            Danno added a comment -

            I suspect this issue will disappear with the announcement that they are rolling JWM into Jira. It would be nice it that could be confirmed here by Atlassian.

            Danno added a comment - I suspect this issue will disappear with the announcement that they are rolling JWM into Jira. It would be nice it that could be confirmed here by Atlassian.

            looking forward to this

            Diego Chavez added a comment - looking forward to this

            "Your feedback is key to helping us understand how you use Jira so we can continue improving your experience. "

             

            Proceeds to discard the feedback, ignore the community, and decides to not improve the experience.
            What a masterclass smh...

            Lorenzo Torresin added a comment - "Your feedback is key to helping us understand how you use Jira so we can continue improving your experience. "   Proceeds to discard the feedback, ignore the community, and decides to not improve the experience. What a masterclass smh...

            Yotawat Poboonwong added a comment - - edited

            Dear Manager of Jira company

            Could you please fix this issue by asap. Because this issue it impact with all company for working. Thank you.

            Yotawat Poboonwong added a comment - - edited Dear Manager of Jira company Could you please fix this issue by asap. Because this issue it impact with all company for working. Thank you.

            I agree 100% with John.  And further, the Summary view for projects seem to pull data from the board, which makes an executive level project view worthless if done items fall off of those charts.  How do I present project health to a Steerco when it doesn't paint a clear picture of the projects deliverables?

            Sean Stokke added a comment - I agree 100% with John.  And further, the Summary view for projects seem to pull data from the board, which makes an executive level project view worthless if done items fall off of those charts.  How do I present project health to a Steerco when it doesn't paint a clear picture of the projects deliverables?

            John Funk added a comment -

            Hi Eric - thanks for the update. However, I don't think this is full transparency. That would include why are you not doing it right now. Other boards have this functionality so it's not that it is something brand new and you have to figure out how to make it work. It would appear it is just a matter of implementing it like other boards. And while you say that the JAC is only one factor in deciding what to do, this request is the top vote getter of open tickets that are not in progress. And it's almost 7 years old. Why in the world would you not do this next? 

            John Funk added a comment - Hi Eric - thanks for the update. However, I don't think this is full transparency. That would include why are you not doing it right now. Other boards have this functionality so it's not that it is something brand new and you have to figure out how to make it work. It would appear it is just a matter of implementing it like other boards. And while you say that the JAC is only one factor in deciding what to do, this request is the top vote getter of open tickets that are not in progress. And it's almost 7 years old. Why in the world would you not do this next? 

            I also have the same problem. When will there be a response to this suggestion? since in the dashboard I can't see more than 2 weeks of issues in each column created.

            Cesar Ramos added a comment - I also have the same problem. When will there be a response to this suggestion? since in the dashboard I can't see more than 2 weeks of issues in each column created.

            Hello, is there any ETA as to when this would be resolved?  The suggested workaround is not sufficient in my case.

            bill.sonnemann added a comment - Hello, is there any ETA as to when this would be resolved?  The suggested workaround is not sufficient in my case.

            the provided "workaround" is not meant to be a solution 

            in the initial request, it is clearly seen that issues are not shown on the board, 

            the suggested "workaround'  just redirects you to a list of issues, which is rather a different thing  

            Please fix this, otherwise, this board does not make much sense or is only for those who have a life-cycle of the issue not more than 14 days. However, it is a work management  type of project so evaluation of completed work can be done on a monthly basis  

            Alexey Gnezdilov added a comment - the provided "workaround" is not meant to be a solution  in the initial request, it is clearly seen that issues are not shown on the board,   the suggested "workaround'  just redirects you to a list of issues, which is rather a different thing   Please fix this, otherwise, this board does not make much sense or is only for those who have a life-cycle of the issue not more than 14 days. However, it is a work management   type of project so evaluation of completed work can be done on a monthly basis  

            A user should have the ability to choose how long items are on a board for.  this should not be different than Jira software kanban boards.

            Tammy Aulston added a comment - A user should have the ability to choose how long items are on a board for.  this should not be different than Jira software kanban boards.

            A sign of good design is consistency. Jira Work Management Board configuration should work consistent to Jira Software. What is this inconsistency saying about Atlassian... a lot!

            Edie Hovermale added a comment - A sign of good design is consistency. Jira Work Management Board configuration should work consistent to Jira Software. What is this inconsistency saying about Atlassian... a lot!

            Valery added a comment -

            I'm not sure why this feature needs so much back and forth. The user of JWM should have the right to decide for how long to keep issues visible, period. Our team repeats many projects on a regular basis, e.g., annual conferences. Replicating all the issues from the previous run makes total sense.

            Valery added a comment - I'm not sure why this feature needs so much back and forth. The user of JWM should have the right to decide for how long to keep issues visible, period. Our team repeats many projects on a regular basis, e.g., annual conferences. Replicating all the issues from the previous run makes total sense.

            ALSHAIKH added a comment -

            please consider this change since it't highly requested by our clients to keep tracking of all TKT's all the time.

            ALSHAIKH added a comment - please consider this change since it't highly requested by our clients to keep tracking of all TKT's all the time.

            The Project Summary view is also impacted. I need to rely on my own query to get a total of all tickets in a project!

            The current obfuscation is unnecessarily time consuming and undoubtedly leads to misreporting. 

            Harvey Buchman added a comment - The Project Summary view is also impacted. I need to rely on my own query to get a total of all tickets in a project! The current obfuscation is unnecessarily time consuming and undoubtedly leads to misreporting. 

            We need to see the issues that are done, this is a big blocker for us. 

            When looking them in the list it's just get too long. why not give the users the option to choose?

             

            yehonathanlu added a comment - We need to see the issues that are done, this is a big blocker for us.  When looking them in the list it's just get too long. why not give the users the option to choose?  

            Kerrie added a comment -

            Another up vote for this. My Product Manager requires a board that shows Done statuses for longer than 14 days and JQL queries just do not cut it 

            Kerrie added a comment - Another up vote for this. My Product Manager requires a board that shows Done statuses for longer than 14 days and JQL queries just do not cut it 

            +1
            Hello, at the very least you should indicate this active time limit of 14 days on the diagrams generated.
            As many people here have already mentioned, I sincerely believe that it should be editable or at least turned it off, otherwise the management tables presented to users will be unusable for longer-term projects.

            Nicolas Spiette added a comment - +1 Hello, at the very least you should indicate this active time limit of 14 days on the diagrams generated. As many people here have already mentioned, I sincerely believe that it should be editable or at least turned it off, otherwise the management tables presented to users will be unusable for longer-term projects.

            This desperately needs to be resolved - it renders so many boards completely useless.

            Rares Finatan added a comment - This desperately needs to be resolved - it renders so many boards completely useless.

            Aleksandr 2easy added a comment - - edited

            We need to have a possibility to reduce count of issues with no resolution. As that we can do in classic Software when configuring board setting and/or sub-filter of kanban board. Really have a big affect on our internal business processes. Workaround is not good idea for us, so why we are need to use JWM project? anyway we need to do separate classic boards...

            Aleksandr 2easy added a comment - - edited We need to have a possibility to reduce count of issues with no resolution. As that we can do in classic Software when configuring board setting and/or sub-filter of kanban board. Really have a big affect on our internal business processes. Workaround is not good idea for us, so why we are need to use JWM project? anyway we need to do separate classic boards...

            Voted for it

            Aleksandr 2easy added a comment - Voted for it

            +8 for this Feature

             

            Its possible to change the time from 14 days in Software Projects, so why shouldn´t it be possible in Business Projects?

            The Board is the most easiest way to get an overview. To take a look into an finished task i have to got to tasks and scroll until i find the right one.

             

            Please add a option with 14 days / 6 month / never

            Alexander Maly added a comment - +8 for this Feature   Its possible to change the time from 14 days in Software Projects, so why shouldn´t it be possible in Business Projects? The Board is the most easiest way to get an overview. To take a look into an finished task i have to got to tasks and scroll until i find the right one.   Please add a option with 14 days / 6 month / never

            Tina Esmaeili added a comment - - edited

            Issues, in any status, suddenly disappeared from my board!  
            no filters

             

            Tina Esmaeili added a comment - - edited Issues, in any status, suddenly disappeared from my board!   no filters  

            Obviously there is a high need for certain project teams to be able to see DONE tasks in their respective boards for more than 14 days. For whatever reasons. 

            As this exact requested feature already exists availably in the LIST view, I am wondering why it takes more than half a decade to get it implemtned in the BOARD view as well? (ticket created Dec. 2017)

             

            Please help accellerate!

             

            Gernot Gugerbauer added a comment - Obviously there is a high need for certain project teams to be able to see DONE tasks in their respective boards for more than 14 days. For whatever reasons.  As this exact requested feature already exists availably in the LIST view, I am wondering why it takes more than half a decade to get it implemtned in the BOARD view as well? (ticket created Dec. 2017)   Please help accellerate!  

            +1 for enabling this feature. I just wasted a good 20 minutes wondering why my project's Board wasn't showing all completed issues (Google to the rescue, eventually led me here). I understand that Boards could quickly get cluttered with many closed issues, but granting us the ability to at least filter out "issues resolved > (xx) days ago" as we please would help appease both sides - those who want the visibility, and those who want minimal clutter.

            Jamie A. Carpenter added a comment - +1 for enabling this feature. I just wasted a good 20 minutes wondering why my project's Board wasn't showing all completed issues (Google to the rescue, eventually led me here). I understand that Boards could quickly get cluttered with many closed issues, but granting us the ability to at least filter out "issues resolved > (xx) days ago" as we please would help appease both sides - those who want the visibility, and those who want minimal clutter.

            Nicolas JACQUEMIN added a comment - - edited

            In my case, I would like to be able to show resolved ticket for more than 14 days. This feature would be a must for marketing projects. I hope you will allow more flexibility in coming months.

            Nicolas JACQUEMIN added a comment - - edited In my case, I would like to be able to show resolved ticket for more than 14 days. This feature would be a must for marketing projects. I hope you will allow more flexibility in coming months.

            Julien SCHNEIDER added a comment - - edited

            I don’t know if being able to update “14 days” delay is a good idea.

            From my point of view, first step is to inform board viewer that some tickets are hidden due to some rules => JWMCLOUD-172

            Julien SCHNEIDER added a comment - - edited I don’t know if being able to update “14 days” delay is a good idea. From my point of view, first step is to inform board viewer that some tickets are hidden due to some rules => JWMCLOUD-172

            Phil Alexander added a comment - - edited

            I couldn't agree with more with Anne-Marie.  It's so weird to have this feature without the ability to at least turn it off.  Please consider this as part of a future product update.

            Phil Alexander added a comment - - edited I couldn't agree with more with Anne-Marie.  It's so weird to have this feature without the ability to at least turn it off.  Please consider this as part of a future product update.

            We just began using Jira and have been very happy with it until this issue came up. This will be a major detriment to the way we operate and potentially a reason to reconsider. Please look into this one. It looks like its been open for quite awhile. 

            Anne-Marie Posgai added a comment - We just began using Jira and have been very happy with it until this issue came up. This will be a major detriment to the way we operate and potentially a reason to reconsider. Please look into this one. It looks like its been open for quite awhile. 

            This 14-day rule is problematic to say the least.  Our senior Management teams need to see ALL workflows for projects in a single view (on the Board) regardless of whether a task or issue is "Done".  There needs to be to be a way to either disable the 14-day feature or give the project manager the ability to modify this or disable all together.  Pls look to build this option into current and future releases of this product.  This is a serious limitation causing problems for departments within my company.

            Phil Alexander added a comment - This 14-day rule is problematic to say the least.  Our senior Management teams need to see ALL workflows for projects in a single view (on the Board) regardless of whether a task or issue is "Done".  There needs to be to be a way to either disable the 14-day feature or give the project manager the ability to modify this or disable all together.  Pls look to build this option into current and future releases of this product.  This is a serious limitation causing problems for departments within my company.

            We definitely need the ability to report everything tracked in a project (clinical trials).  We must retain the numbers reported to leadership and funders, for projects that run 5-10 years.

            Jacki Mallmann added a comment - We definitely need the ability to report everything tracked in a project (clinical trials).  We must retain the numbers reported to leadership and funders, for projects that run 5-10 years.

            Our use case is quite different from most and this really hinders our reporting as we report on the status of EVERYTHING tracked in a project, not just what is "open" or "in progrees". We recently moved to cloud and were so pleased with the Summary and Board views but removing the "done" status issues after 14 days renders these views useless for us. If this must be a feature of this board than it should be something we can turn off.

            Jessi Smith added a comment - Our use case is quite different from most and this really hinders our reporting as we report on the status of EVERYTHING tracked in a project, not just what is "open" or "in progrees". We recently moved to cloud and were so pleased with the Summary and Board views but removing the "done" status issues after 14 days renders these views useless for us. If this must be a feature of this board than it should be something we can turn off.

            Stacy S added a comment - - edited

            Also, I can confirm we are missing tickets in our "Needs Reviewed" and "In Progress" columns as well (even after trying to comment on them, move them between columns, edit their description, etc.), NOT only Done, so either the documentation on this page is incorrect or this is a bug, as Sandra noted: https://community.atlassian.com/t5/Jira-questions/Business-Project-issues-dissapear-from-board/qaq-p/874080.  No amount of activity enables a ticket to show again once it's reached two weeks on the board, which is ABSURD.

             

            Edit to Add: After realizing the missing tickets were all of one issue type, I dug into it further.  Apparently the issue I'm experiencing is due to the fact that once multiple workflows are created for a project, you can no longer see all tickets in one view on the board (at least that I have found so far).  You instead have to toggle between workflows in order to see each subset of tickets that fall under that particular workflow. 

            While not the exact same issue, it's still absurd that the board operates this way and I can find no documentation on why or even clarity that the business project operates this way, beyond Joshua's comment in the following post.  https://community.atlassian.com/t5/Jira-Software-questions/Can-t-see-all-issues-on-a-Business-Project-Board/qaq-p/2085653

            Stacy S added a comment - - edited Also, I can confirm we are missing tickets in our "Needs Reviewed" and "In Progress" columns as well (even after trying to comment on them, move them between columns, edit their description, etc.), NOT only Done, so either the documentation on this page is incorrect or this is a bug, as Sandra noted: https://community.atlassian.com/t5/Jira-questions/Business-Project-issues-dissapear-from-board/qaq-p/874080.   No amount of activity enables a ticket to show again once it's reached two weeks on the board, which is ABSURD .   Edit to Add: After realizing the missing tickets were all of one issue type, I dug into it further.  Apparently the issue I'm experiencing is due to the fact that once multiple workflows are created for a project, you can no longer see all tickets in one view on the board (at least that I have found so far).  You instead have to toggle between workflows in order to see each subset of tickets that fall under that particular workflow.  While not the exact same issue, it's still absurd that the board operates this way and I can find no documentation on why or even clarity that the business project operates this way, beyond Joshua's comment in the following post .   https://community.atlassian.com/t5/Jira-Software-questions/Can-t-see-all-issues-on-a-Business-Project-Board/qaq-p/2085653

            Stacy S added a comment -

            Adding to the many comments re: the absurdity of this "feature", as well as complaining that this was reported more than FIVE YEARS AGO, with no acknowledgement or progress from Atlassian.  This would have been a dealbreaker for us if we hadn't figured out a workaround!

             

            I assume most of you will have given up by now, but if not, there is another workaround I've discovered (which is ridiculous we're even forced to use, but it is what it is...):

            If you create a new Kanban board on another company-managed project, you can ignore the company-managed project's issues, only pull in your team-managed project's tickets in the filter query, and set the "Hide completed issues older than" to different week values or set it to "Never mind, show all". 

            It's far from perfect, but it's at least enabling us to actually use the team-managed project as WE intended (not this absurd two-week rule).

            Stacy S added a comment - Adding to the many comments re: the absurdity of this "feature", as well as complaining that this was reported more than FIVE YEARS AGO, with no acknowledgement or progress from Atlassian.  This would have been a dealbreaker for us if we hadn't figured out a workaround!   I assume most of you will have given up by now, but if not, there is another workaround I've discovered (which is ridiculous we're even forced to use, but it is what it is...): If you create a new Kanban board on another company-managed project , you can ignore the company-managed project's issues, only pull in your team-managed project's tickets in the filter query, and set the "Hide completed issues older than" to different week values or set it to "Never mind, show all".  It's far from perfect, but it's at least enabling us to actually use the team-managed project as WE intended (not this absurd two-week rule).

            We have a team-managed Jira Work Management project. There are issues that have the status "zur Information" (=done) that are NOT SHOWN in the board in the column "zur Information"
            BUT they appear under "list".

            It is very important for us to see ALL issues in the board-column, especially because the client has access to this board and checks the issues there!

            The Atlassian support team told me that the issues are removed from the board after 14 days. Why 14 days? Why is it not possible to edit the time myself?

            Please fix this because it affects how the client sees the project overall.

            Julia Fischer added a comment - We have a team-managed Jira Work Management project. There are issues that have the status "zur Information" (=done) that are NOT SHOWN in the board in the column "zur Information" BUT they appear under "list". It is very important for us to see ALL issues in the board-column, especially because the client has access to this board and checks the issues there! The Atlassian support team told me that the issues are removed from the board after 14 days. Why 14 days? Why is it not possible to edit the time myself? Please fix this because it affects how the client sees the project overall.

            This is a must have feature, cannot believe it is not been implemented. When will this be approved???

            Ruben Ribeiro added a comment - This is a must have feature, cannot believe it is not been implemented. When will this be approved???

            What everyone else has said. It is a pretty reasonable request - if you are selling this as a tool for managing operations - there is even a 'leads' template project! 

             

            Just like the list in the same project - add a button to show "Done" issues so you let the user choose! 

             

             

             

            Seán Kinsella added a comment - What everyone else has said. It is a pretty reasonable request - if you are selling this as a tool for managing operations - there is even a 'leads' template project!    Just like the list in the same project - add a button to show "Done" issues so you let the user choose!       

            It's crazy.  We actually moved to Asana for our more robust operations work specifically because of this issue.  

            Michelle Hirons added a comment - It's crazy.  We actually moved to Asana for our more robust operations work specifically because of this issue.  

            Martin Kay added a comment -

            What Kari and Steven said.

            Martin Kay added a comment - What Kari and Steven said.

            I discovered this AFTER, I recommended this type of project to several departments. This is very stupid. Please fix.

            Steven Camilleri added a comment - I discovered this AFTER, I recommended this type of project to several departments. This is very stupid. Please fix.

            Seems to be the third most voted issue in "Open Issues" list... Is it time to do something about it?

            Kari Kiviniemi added a comment - Seems to be the third most voted issue in "Open Issues" list... Is it time to do something about it?

            Martin Kay added a comment -

            What Adithya said ! 

            Martin Kay added a comment - What Adithya said ! 

            Hello Jira team,

            There has been several requests from the community for this feature and the we would highly benefit from the implementation.

            Your team has been really active in finding duplicate requests such as https://jira.atlassian.com/browse/JWMCLOUD-21, but has not provided the community with any update on this request. 

            I kindly request your team to genuinely gather interest and work on providing us this feature in the next release!

            Adithya Viswanathan added a comment - Hello Jira team, There has been several requests from the community for this feature and the we would highly benefit from the implementation. Your team has been really active in finding duplicate requests such as https://jira.atlassian.com/browse/JWMCLOUD-21 , but has not provided the community with any update on this request.  I kindly request your team to genuinely gather interest and work on providing us this feature in the next release!

            Hi, 

            This is rather funny that Jira itself blocks issues in strange statuses such as "Gathering Interest". I can see that this issue was created in 2017. What an agile development!

            I'm looking forward to a fix too and voted for this issue.

            Best,

            Nicolas.

            Nicolas Wajs added a comment - Hi,  This is rather funny that Jira itself blocks issues in strange statuses such as "Gathering Interest". I can see that this issue was created in 2017. What an agile development! I'm looking forward to a fix too and voted for this issue. Best, Nicolas.

            Danno added a comment -

            I still don't understand the disconnect on this. How is it that JWM is different than Jira Software in this regard? I found out the hard way after building a Purchase Requisition project using the business template. I had no idea the issues would drop off the board after 14 days of inactivity. By the time I discovered this "feature" I had over 1000 issues in the system. I had to create a new software project to migrate them to which caused even more trouble since the issue key numbering was now different.

            My point here is if they aren't going to fix the feature why isn't prominently displayed in the documentation so you can decide if it is acceptable? There should be a disclaimer in the create a new project wizard.

            Danno added a comment - I still don't understand the disconnect on this. How is it that JWM is different than Jira Software in this regard? I found out the hard way after building a Purchase Requisition project using the business template. I had no idea the issues would drop off the board after 14 days of inactivity. By the time I discovered this "feature" I had over 1000 issues in the system. I had to create a new software project to migrate them to which caused even more trouble since the issue key numbering was now different. My point here is if they aren't going to fix the feature why isn't prominently displayed in the documentation so you can decide if it is acceptable? There should be a disclaimer in the create a new project wizard.

            ZC added a comment -

            really 5 years for this!? anyone from Atlassian support watching?

            ZC added a comment - really 5 years for this!? anyone from Atlassian support watching?

            I commented on this years ago and we gave up finally and moved our sales process to a real CRM - first Copper then Streak and now we've settled on Pipedrive.  I would never usually leave an update like this because I love Jira for other things - but not for sales and not for hardware/personnel tracking where you need to have stories/tickets stay on the board.  

            Michelle Hirons added a comment - I commented on this years ago and we gave up finally and moved our sales process to a real CRM - first Copper then Streak and now we've settled on Pipedrive.  I would never usually leave an update like this because I love Jira for other things - but not for sales and not for hardware/personnel tracking where you need to have stories/tickets stay on the board.  

            This is a must have feature 

            We use the boards functionality on Jira Work Management to manage order confirmations, contracts, sales and customers. A potential order starts as "Create Quote" and - after an approval process - is moved to the "Customer has confirmed Quote" column. The last column "Invoiced" acts as a "Done" column.

            Sometimes it takes longer than 14 days for a customer to accept the offer. Sales should dig deeper here. It is therefore important that the tickets do not disappear after 14 days.

            Neither in the intermediate columns nor on the final "Done" column.

            A "Show older tickets" link would be okay too - but letting them disappear without a word is extremely distracting and a showstopper.

            => I think the time period until tickets disappear from the board should be configurable.

            Andreas Schwinger added a comment - This is a must have feature   We use the boards functionality on Jira Work Management to manage order confirmations, contracts, sales and customers. A potential order starts as "Create Quote" and - after an approval process - is moved to the "Customer has confirmed Quote" column. The last column "Invoiced" acts as a "Done" column. Sometimes it takes longer than 14 days for a customer to accept the offer. Sales should dig deeper here. It is therefore important that the tickets do not disappear after 14 days. Neither in the intermediate columns nor on the final "Done" column. A "Show older tickets" link would be okay too - but letting them disappear without a word is extremely distracting and a showstopper. => I think the time period until tickets disappear from the board should be configurable.

              sguio sguio
              skorte Soane Korte (Inactive)
              Votes:
              521 Vote for this issue
              Watchers:
              315 Start watching this issue

                Created:
                Updated:
                Resolved: