Is it possible to add custom logic using Forge in Jira Cloud to sync an issue title in the All Work

[Rosalin kandapan]

Is it possible to add custom logic using Forge in Jira Cloud to sync an issue title in the All Work → List view?

For example, I created a custom dropdown field called Affected Epics for the Story issue type using Forge. When I select a value from the Affected Epics dropdown, it appears correctly in the All-Work list view for the Story work item under the Affected Epics column.

However, there is a problem:
If I change the Epic work item’s title from “Epic1” to “Epic1 updated”, the updated summary is not reflected in the Affected Epics column in the list view.

Currently, we store the value in the following format:
JAP-1 Task1 (as a string)
When the Task summary changes from “Epic1” to “Epic1 updated”, the All-Work list view still shows the old value because it was saved only at the time the Story was created.

When we manually select the “Task1 updated” option from the Affected Epics dropdown on the Story work item, the updated summary is displayed correctly under the Affected Epics column in the All-Work tab.

so, problem is automatically sync not happening on click on refresh in All work tab page.

Is there any way to automatically sync the Epic summary with the Affected Epics field in the Story work item?

[Tuncay Senturk _Snapbytes_]

Hi @Rosalin kandapan 

That's a good and tough question, but here is my two cents on this. Please take it with a pinch of salt.

In the list view, Jira shows the stored field value. For a Forge custom field, that's what you saved (like JAP-218: Epic D). When the epic's summary changes, Jira does not re-compute other issues' custom field values, and the list view refresh does not trigger the Forge code. And as far as I know Forge does not give a hook to overcome this.

However I'd suggest posting this to the Atlassian Developer Community, I trust there are more experts there to answer this.