Request for Solution: Capturing Multiple Values per Field in a Single Issue in JSM

[Muammad Faizan Iftikhar]

Dear Members,

We are currently working on a use case in Jira Service Management where we need the ability to retain multiple values per field on a single issue over time.

Current Limitation:
In the standard Jira setup, each field on an issue can store only a single value. If the field is updated through the issue screen, the previous value is overwritten and cannot be retained unless tracked manually or through issue history. This limits us to capturing only one data point per field per issue.
Even though we are using Table Grid Next Generation, it relies on data coming from issue fields. Since issue fields can only store one value at a time, we are only able to populate a single row per issue in the grid.

What We Need:
We're looking for a way to capture and retain multiple values for the same field within a single issue.

[Petru Simion _Simitech Ltd__]

Hi @Muammad Faizan Iftikhar ,

You can write a scripted field that will parse automatically the issue history and display all the historic values the way you chose. 

The advantage is that it will work with existing data as well as new data.

Other solutions, such as capturing the values in another field, every time the field of interest is changed will only work from the moment you implement the solution, while the scripted field will not have this problem.

Alternativelly, if you are open to using apps, you can use Issue History Dashboard for Jira (Work Item History) , an app developed by our company.

You can filter by Field Updated = [Your field]

The Value From and Value To columns will display the value of the field before and after the change.

You can export your result to CSV for further analysis and processing.

Regards, 

Petru

[Aron Gombas _Midori_]

To me, this use case is a bit strange, but a totally trivial automation rule could solve it. I assume you want to track the historical values of a field because you wrote "over time".

Let's say you have the field "Foo" and you need the 3 most recent values to know.

Steps:

1. Add another field "Foo (prev)" (same type as "Foo").
2. Add another field "Foo (prev 2)" (same type).
3. Create an automation rule which:
   1. Is triggered by the changes of the "Foo" field (after the new value was saved).
   2. Copies the current value of "Foo (prev)" to "Foo (prev 2)".
   3. Set the value of "Foo (prev)" from the smart value which is passed to the automation rule and carries the old value of "Foo".

With this approach, you have 3 separate fields (you can add them to any screens) that capture the current ("Foo"), previous ("Foo (prev)") and the previous to previous ("Foo (prev 2)") values.

[Marc - Devoteam]

Hi @Muammad Faizan Iftikhar 

You will need to create a multi select field for this.

[Pedro Olmo]

Hello @Muammad Faizan Iftikhar ,

A field contains a single value per work item. In case it is a multi-select field, it can have multiple values. The option you mentioned with the Next Generation table grid might work for you to create tables where you can place the value of a field n times.

Regards