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; } } }

Smart tags?

András Taraszovics

Hello, we have built our product development process using JPD and Jira Software. Part of the process is triaging new ideas and letting the requestors know if there idea did not make it to the next stage of the product development process.

Currently this happens through the Comments area where we need to manually tag the requestor (E.g. @ Joe Doe), however it would be much more convenient (and easier to automate) to have a dynamic (smart) tagging option which can automatically tag the correct stakeholder (e.g. @ Requestor, @ Creator, @ Assignee etc.).

Is this something that is possible or will be possible in the near future?

Accepted answers

Clark Everson

Hi @András Taraszovics

It should be possible using a field in JPD. You would do it through automations. There maybe prebuilt ones, otherwise you can build your own

https://www.atlassian.com/software/jira/product-discovery/guides/automation/overview#automation-templates

Best,

Clark

All comments

Clark Everson

Hi @András Taraszovics

It should be possible using a field in JPD. You would do it through automations. There maybe prebuilt ones, otherwise you can build your own

https://www.atlassian.com/software/jira/product-discovery/guides/automation/overview#automation-templates

Best,

Clark

Tanguy Crusson

Correct (and thanks @Clark Everson !). The only way to do this today is via an automation.

We are going to start revisiting Feedback and Insights and this should cover your need, but it's not there yet.

András Taraszovics

Thanks @Clark Everson for the suggestion, let me elaborate on the exact workflow as I failed to include that in the first place.

We tend to provide a short explanation along with marking the idea obsolete so the reporter knows the precise reason for why their idea got rejected. An example could be something like this:

Dear Requestor,

The support lifecycle for our SOAP API ended in 2024 and we are phasing out those APIs effective 1 January 2026. Unfortunately, this means that we will not include these APIs in our new Postman collection.

Thank you for your understanding.

The important bit here is that every message is tailored to the particular idea so it is not something that we can automate.

Kind regards,
Andras