Functionality missing for Full Admins

Question

Hello!  A couple bugs have just popped up for us, please:

* Lost ability to add comments and link issues of archived tickets
* The predictive field doesn’t seem to be working for me.  Ex:  Key Customer field.  I was able to reproduce this on other tickets, and the ticket is not archived.

Confirmed that we have full admin access.  Thank you!

Jack Arndt · Answer

@Hermance NDounga

Thank you for the suggested workaround. I'm wondering if the Jira Product Discovery team has any plans on the roadmap to better support large volumes of ideas across multiple teams and projects?

From my internal sandbox testing, managing thousands of unarchived ideas in a single project starts to become unwieldy and poses performance challenges in areas like search, filtering and cross-project visibility.

Do you have guidance on how many active ideas a project can robustly support before it becomes too large? And are there any future plans to facilitate segmentation and visibility across multiple discovery projects that you can share?

While your proposed custom field filters help in the short-term, I'm looking for a more sustainable solution to scale discovery long-term across our 20+ product teams.

If not through more flexible archiving, are there any other solutions you'd recommend exploring to avoid hitting the limits of a single project?

Hermance NDounga · Answer

Hello Jack,

The archive feature isn't a Jira Product Discovery-only feature. It's a feature that exists also in our Data Center products, and is the same across all Jira products in the Cloud - archived ideas aren't editable.

Archived ideas can be unarchived if there are still traction around them, but ultimately yes, that feature should be use to remote them from search queries and avoid polluting current work.

If in your discovery process, you sometimes need to prioritize ideas for future consideration, then I'd suggest to create a field, for a example a select field, in which options are "Prioritized, Under Consideration, Deprioritized, Future consideration". Or if you have a roadmap field, just adding an option "future consideration" would enable you to have a a global view of all your ideas (which is not possible if you archive them) , while being able to filter them out of short term roadmaps.

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

Jack Arndt · Answer

Dear @Hermance NDounga

As a valued customer working to scale Jira Product Discovery across 20 teams in my organization, I was disappointed to hear the rigid perspective on preventing any editing or linking of archived ideas.

While I understand the intention is to treat archives as fully completed work, this narrow definition ignores numerous valid use cases like mine where archives serve as reprioritization buckets for future consideration.

Given the current limitations in scaling discovery across multiple projects, we are constrained into tracking all teams under one Jira Product Discovery project. In conversations with your support team, they acknowledged the challenge of managing our volume under a single project and could not provide guidance on supporting multi-project visibility.

With that context, enforcing a permanent lockdown of archived ideas severely restricts our ability to flexibly manage a large backlog of both active and reprioritized ideas in one central place.

I believe Atlassian has an opportunity to better support customers like us by taking a more configurable approach. Rather than dictating a single view of archives, allow admins to customize archiving permissions to meet their needs.

This would empower your loyal users while still giving the option to lock down archives for those who want it. I hope you will reconsider this restrictive stance and work collaboratively with us on a solution that serves all use cases. Please let me know your thoughts on how we can partner to make this tool work at our scale.

Thank you for your time.