Description
Often you need to create a standard set of Confluence pages or JIRA Jira issues or similar. The Run CLI Actions in Confluence allows you to semi-automate this process using the power of ACLI. The process or activity is easily documented and readily changeable. Confluence page history provides tracking. The RUN should be used to provide a run button and to parameterize some of the data - the technique is demonstrated in Repetitive task using the RUN macro. An alternative is to use the --simulate parameter on the run action and manually remove it when ready to run the actions using preview mode.
Confluence example
| No Format |
|---|
|
{cli:profile=confluence}
--action run --common "--space zcli"
@DATA:
--action storePage --title "Designs"
--action storePage --title "Design 1" --parent "Designs"
--action storePage --title "Design 2" --parent "Designs"
# Remove comment for this only for UI projects!!!
# --action storePage --title "UI Design 1" --parent "Designs"
{cli}
|
...
| No Format |
|---|
|
Run: --space zcli --action storePage --title "Designs"
Page updated: 'Designs'. Page has id: 86245981
Run: --space zcli --action storePage --title "Design 1" --parent "Designs"
Page updated: 'Design 1' as child of 'Designs'. Page has id: 86245982
Run: --space zcli --action storePage --title "Design 2" --parent "Designs"
Page updated: 'Design 2' as child of 'Designs'. Page has id: 86245983
# Only do this page for UI projects
# --action storePage --title "UI Design 1" --parent "Designs"
Run completed successfully. 3 actions were successful
|
...
Jira example
| No Format |
|---|
|
{cli:profile=jira}
h3. JIRA example
{cli:profile=jira}
--action run --common "--project zcli"
@DATA:
--action createIssue --type task --summary "Task 1"
--action createIssue --type task --summary "Task 2"
{cli}
|
...