Adding Insights to Archived Ideas
Asked by Jack Arndt:

Greetings,  
I am writing to address a matter of concern that has arisen within our user community pertaining to the inability to append insights to archived items.  
This issue has given rise to a sense of frustration among our users. Allow me to outline two fundamental use cases that underscore the significance of rectifying this situation:  

1. Our end users often find themselves in a scenario where they possess additional justifications that they wish to associate with an archived item, thereby imparting insights that can contribute to the re-evaluation of the item's archived status.
2. Our Product Managers, as a strategic approach, opt to archive items that are slated for consideration beyond the scope of the upcoming two quarters. This approach serves to maintain the focus of our board on the immediate two quarters. Regrettably, the prevailing limitation hampers our PMs from affixing pertinent insights to these items situated in the distant future.

It has come to light that the prevailing workaround, involving the process of "unarchiving," appending insights, and subsequently "re-archiving," is proving to be a suboptimal approach, leading to a less-than-ideal user experience.  
Given these challenges, I am reaching out to our esteemed community for insights and recommendations on alternative avenues that could be explored to address this concern more effectively.


Answers:
author: Rohan Swami
body: Hi [@Jack Arndt](/t5/user/viewprofilepage/user-id/2764779) I have a similar recommendation to [@Omar Bennani](/t5/user/viewprofilepage/user-id/5130353) .

We find that it's still helpful to have those ideas in an unarchived state so that you can still: Add insights, fill in field values (eg. list of customers requesting this feature) even if those ideas are not your immediate focus.

comments: author: Jack Arndt
body: That makes sense, we adopted the policy as we had performance limitations concerns with keeping many issues in our main project.  

We may just need to alter our approach.  

[@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658) do you know how many unarchived issues a JPD project can handle before it starts to see performance/slow-down issue?


author: Rohan Swami
body: [@Jack Arndt](/t5/user/viewprofilepage/user-id/2764779) a couple of hundred issues perform fine, and we're investing heavily at the moment in scale and performance to improve this further.


author: Kei Hau
body: [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658) What happens if we exceed a couple of hundred ideas? Is there another workaround Atlassian can suggest? And when can we expect performance to improve further?


author: Rohan Swami
body: [@Kei Hau](/t5/user/viewprofilepage/user-id/3555720) there aren't limits on how many ideas you can have, things will load a little slower and interactivity becomes a bit laggier as numbers get higher. We're shipping improvements to scale and performance every week, some big and some small.


author: Omar Bennani
body: I think the long and the short of it is stop archiving issues. Archiving is special to really take things out, and should include things you've completed as well as aren't going to do. If you want to focus on the next two quarters filter the views to only look at those roadmap values.

Another option, if the focus is on the next two quarters, be explicit to your end users. We have a 'Won't do' status to indicate an idea won't be done ever. You should have that, but you could add another to say 'Won't do now' or 'Won't do soon' or however you'd like to phrase it. That makes it clear to users and will leave your items easily findable.