Currently, I am implementing an application that updates Confluence pages triggered by Jira ticket creation and update.
When Jira tickets are updated continuously in a short period of time, multiple Confluence page update processes run at the same time.
As a result, the process does not work properly.
I would like to make the page update processes that run sequentially instead of in parallel.
If anyone knows how to do this, I would appreciate your help.
Thanks for your help.
Hey,
Are you using Forge Product events to capture Jira updates? Then use that product event to update Confluence page?
Can you describe a bit more detail on what you mean by “As a result, the process does not work properly.”
Cheers
Ben
Are you using Forge Product events to capture Jira updates? Then use that product event to update Confluence page?
The below is the part of manifest.yml. index.run is triggered by “avi:jira:updated:issue” or “avi:jira:created:issue”, Confluence pages are updated
modules:
trigger:
- key: release-note-automatic-update-app-hello-world
function: main
- avi:jira:created:issue
- avi:jira:updated:issue
filter:
ignoreSelf: false
expression: event.issue.fields.project.name == 'Test2'
function:
- key: main
handler: index.run
Can you describe a bit more detail on what you mean by “As a result, the process does not work properly.”
For example, if two processes that append rows to a table on a page run simultaneously, they may not work.
Ideal:
Initial page: row A
After process 1: row A + row B
After process 2: row A + row B + row C
Actual:
Initial page: line A
After process 1: line A + line B
After process 2: line A + line C
Thank you very much !
Sorry for the delay on my response.
Could you use those Jira triggers to store the computed result in Forge KVS or Forge SQL and then when you render in Confluence you can determine the correct order to display?
I think that a process is triggered by a Jira event (in this case, issuing or updating a ticket).
Is there any way to make it so that when a ticket is updated (trigger 1, trigger 2) in succession, the process called for by trigger 2 does not start until the process called for by trigger 1 is completed?
