Functionality missing for Full Admins

[Rachael Green]

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

1. Lost ability to add comments and link issues of archived tickets
2. 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]

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.

[Hermance NDounga]

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]

@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]

Hey Rachael, 

Archived ideas have a banner saying that this issue is achieved and cannot be edited or linked to other ideas, and the fact that you were able to edit them or link them to other issues was a bug 😅

Can you please elaborate on your use case on when you need to work on archived ideas? 

For your key customer field, can you please let me know what field type is it (people, select, multiselect ...), and what's the behaviour that you are experiencing instead - for example you type 3/4 letters and nothing appears or the list doesn't get reduced? 

[Rachael Green]

Hi Hermance - thank you for your response.

Adding comments to archived ideas would be very useful as customers may be following up with new discovery or priority feedback.  By allowing comments to archived ideas, this allows JPD to be the source of all comms between Product and the requestors.  By allowing users to link delivery other ideas or related ideas, this allows for a robust, transparent picture or any related or duplicate ideas which could be especially helpful during the Discovery phase.

For the predictive behavior, I'm entering in chars and the list of potential customers is not rendering. 

Hope this helps!

[Hermance NDounga]

Hello Rachael, 

For the list not loading could you please open a ticket with our support engineers - so they can investigate directly on your site? I'm not able to reproduce the issue on my end, but that's definitely a problem that needs to be solved. 

https://support.atlassian.com/contact/#/

For the archiving, we are now aligned with how archived projects and archived issues work in the Jira platform (Jira Software, Jira Service Management and Jira Work Management). 

I think in theory an archived idea is an idea that has been fully shipped and done, maybe weeks/months ago and for which you don't receive feedback anymore - or at least, you're not in the discovery phase for this idea. 

If you still have delivery tickets to be linked to this idea, I would suggest to un archive it, because the implementation for this idea is not over, and it makes it an active (still being worked on) idea. 

Same if you receive new feedback regarding an archived idea - if you want this feedback to be counted in your prioritization process, you might want to unarchive this idea, because all archived ideas are excluded from all other views - so you cannot have one global prioritization view that contains both the archived and the active ideas. 

Best Regards,
Hermance
Product Manager @ Jira Product Discovery