nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to close an Idea ticket?

Jeny Stoeva

Hi,

I am wondering why the ideas tickets in a "Done status" according to the workflow, are not visually indicated as Closed (with a strikethrough) like any other Jira ticket? Will this be implemented for the Ideas too?

When the Idea tickets are in Done status for longer than e.g. 2 weeks would it be possible to configure the option to hide the older ideas via the "Hide completed issues older than" feature available on the software project boards and enable search for them via a link in the board column? I guess no one would like to keep on the board a long list of long time closed ideas.

Accepted answers

All comments

Eugen Stolin

My understanding is that you use "Archive" for that.

There is a possibility to archive ideas. There is also a list of the archived ideas just above "Project settings" in the left menu.

My guess is that it can be automated, where you move "done" to archive after x amount of days, but tbh I haven't tried it yet.

Jeny Stoeva

Hi @Eugen Stolin ,

I am aware of the Archive and still I am missing the visual indication for the Closed status.

It would be great if there is an option to simply configure after what period the closed ideas should be moved to Archive, instead of all of us attempting to automate it. I am not sure if that is even possible but will try it out, thanks for this suggestion

Jon Watts_4xvzzl

Hi @Jeny Stoeva

Check out this article regarding Best practices on using the "Resolution" field in JIRA Cloud products.

https://confluence.atlassian.com/cloudkb/best-practices-on-using-the-resolution-field-968660796.html

Best regards
Jon

Jeny Stoeva

Hi @Jon Watts

I could only say that I would love to have a Resolution field in the JPD but it is not there from what I see.

JPd looks like a team managed project (and not a company managed one, for which this article is about) and if there would be a Resolution it would be set automatically when the tickets is moved to a "Done status" with no option to configure different Resolutions e.g. "Won't do", "Duplicate" etc.

I would like Atlassian Team to share what is their plan for the JPD.

Jeny Stoeva

@Eugen Stolin Interestingly when you open a delivery ticket associated with a closed idea in the delivery ticket (which is in a software project) the linked idea is striked-through, just not in JPD.

Eugen Stolin

@Jeny Stoeva I understand your point! We prefer to work with boards and in that case it's not a big of an issue. But it's always nice to have consistency.

Hermance NDounga

Hi Jenya!

Thank you for your feedback. Regarding the "idea lifecycle", we mainly wanted to make things flexible, so all teams are able to decide how they manage their workflow, and not enforce a specific way of working.

The backlog in Jira has a very specific function: you plan tasks in a sprint; along the sprint when some tasks are resolved/done they get crossed for visibility, and then they disappear from this screen when you start a new sprint.

The list view in Jira Product Discovery isn't specifically meant to be a backlog of ideas: it can be set up in any way, for multiple purposes, some in which you would want to keep and see your "Done" ideas.
For example, if you would want to be able to report on all the ideas you tackled last year and share this with your stakeholders and managers: in that case, sharing a view where all ideas have a strikethrough would be counterintuitive and maybe confusing, especially for people who aren't used to Jira Software.

On the other side, some of our users do not use the "Status" field to track the progress of an idea, but a simple multi-select field, for example, a roadmap field with the options "Now, Next, Later, Done".

Finally, some product teams would archive these "Done" ideas, some others would prefer to not archive them but simply to filter them out of some views to be able to report on them on other views (whether they track them via the Status field or a simple multi-select field).

As the ideas can be more flexible entities than stories or tasks in Jira, we think the way you handle them once they are "done" should also be more flexible.
Now, I think we could definitely do a better job at explaining this somewhere , so thanks again for your feedback!

Cheers,

Hermance

Jeny Stoeva

Hi @Hermance NDounga ,

Thanks for taking care to explain, I appreciate it! I understand where you are coming from. I also think you contradict a bit your own argumentation

Providing more flexibility would mean for me to allow the users to decide if they want to close the ideas visually too (with a strike through) and not deciding to have the tickets always visually open. It would be a nice thing to have that choice but even more helpful would be to enable an automatic ideas archiving based on status or/and specified time period.

Why I think it is valuable is because eventually every ticket comes to the end of its lifecycle or simply becomes obsolete/outdated and instead of using views and filters to try to hide those tickets it would be great to have the opportunity to configure when a ticket should be moved to the archive. I am currently not seeing any options to automate it.

Cheers,

Jeny

Martijn ten Caat

I would like to have a Closed status as well, the reason to use JPD is to streamline work and to streamline it I need to have the Jira status Closed available in JPD.

If I have to create a new status Closed (which would be duplicate to the Jira status Closed) I then would have to check all automations, filters and workflows.

So, as a user of both Jira software and Jira Product Discovery I would like to have the Jira statussen available in JPD to streamline work and minimize education to internal and external users of our site.

Martijn ten Caat

An idea which is duplicate or which is so bad that we are not going to implement should get the end status Closed to show it's handled correctly but it's not developed...

Welcome!

It looks like you're new here. Sign in or register to get started.