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

Add Status to Summary when transitioning

Hans Petter Farstad_pddu0v

We have a column that is called Done/Refused, and I want to make it easier to differentiate between those two Statuses by having an automation that added the Status to Summary (in addition to the original content). An example: "Summary = Test1" when Status is updated to "Refused" the Summary now becomes "[Refused] - Test 1".

Thanks in advance!

Accepted answers

Burak Bal

Hi Hans,

You can create an automation rules like below.

You need to use smart values. You can update the summary field as [{{issue.status.name}}] - {{issue.summary}}. You can use the Issue transitioned trigger.

All comments

Jack Brickey

Hi @Hans Petter Farstad , If this is a company managed project, I would recommend using the resolution field for this purpose. That is, when an issue has moved to "done" the user would be required to add the resolution value - "done" or "refused".

Burak Bal

Hi Hans,

You can create an automation rules like below.

You need to use smart values. You can update the summary field as [{{issue.status.name}}] - {{issue.summary}}. You can use the Issue transitioned trigger.

Nic Brough -Adaptavist-

Jamming data into the summary of an issue suggests that you've come from a "legacy" system that doesn't work the way you would like it to.

I usually find this sort of "ask" coming from people who are used to Remedy, Lotus Notes, ServiceNow and HP trackers which are hard to get useful data out of (unless they have really really good admins) and "botch fields into somewhere we can actually use" is the best way to fix the problem when the admins can't work around it.

Your best approach is to use fields as intended. As @Jack Brickey suggests, the resolution field feels like the right place here, unless there's some subtlety we are missing.

TLDR: Summary is the wrong place to do this. Use resolution and status as Atlassian have built them, it's far better. (I've got some qualms about resolution, but that's another story)

Hans Petter Farstad_pddu0v

It is a company-managed project yes. The reason behind this question is that I want it to be easier to quickly gain an overview over what is Done and what is Refused without having to open the card themselves.

We are currently using Colour Code based on Component as a way to differentiate between Done and Refused, but people easily ignore the small colour field on the left of the card and/or easily forget which is what. People in this context are managers, other decision-makers and/or infrequent users of Jira.

We also currently use the additional three extra fields for other purposes and as far as I can tell there is no way to customize card layout based on Column and/or Status (excluding Scrum-boards).

So I know it is an ugly solution, but the thought was that it hopefully adds additional clarity to some of our boards.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

kanban