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

Watcher automation from Confluence to Jira

Sherry Nightingale

I have an automation rule from Confluence to Jira that states:

When the status is changed on a Confluence page create a task in a Jira project and auto populate a required set amount of fields

I've added a 'Then: add an action > and manage watchers and included the names but when I run the test the names aren't added as watchers

They need to be added as watchers when the ticket is created on status change in Confluence

Any guidance greatly appreciated

Accepted answers

All comments

Marc -Devoteam-

Hi @Sherry Nightingale

Can you share your automation rule as a screenshot, this helps members to look at your configuration and maybe see the issue directly.

Sherry Nightingale

Confluence Automation Rule.PNG

Sherry Nightingale

@Marc -Devoteam-

I've provided the confluence automation rule screen grab

Marc -Devoteam-

Hi @Sherry Nightingale

The add watchers in Confluence automation, you can add or remove watchers from pages or blog post.

I think the only solution is to create in Jira that check on issues created in the project and add the watchers.

Sherry Nightingale

@Marc -Devoteam-

Just to clarify - are you saying that I should create an automation rule in Jira that when a ticket is created automatically from a Confluence automation rule that watchers are added?

Thanks

Sherry

Marc -Devoteam-

Hi @Sherry Nightingale

Correct, as the add watchers option for Jira issues only exists in automation on Jira.

Sherry Nightingale

Thanks @Marc -Devoteam-

How would I set / create this automation rule - what would I need to tell it?

Trigger > when: issue created

Then: Edit issue fields

And: Add watchers

????

But how can I get this rule to run when certain tasks are created via the Confluence automation rule?

Marc -Devoteam-

Hi @Sherry Nightingale

Add conditions, like;

- only in project

- type of issue

- reporter equals

- creator equals

- other differentiations that are set in the created issue from the automation in confluence, labels, components, custom field values, etc...

Choose the ones that apply.

Marc -Devoteam-

Hi @Sherry Nightingale

That would work, but in your rule in Confluence, I also see the field Business Unit, Strict Embargo, etc..

If any of these fields are mandatory on issue creation, you could use these as well. or if they need to contain a value.

Sherry Nightingale

@Marc -Devoteam-

I looked at all of the fields and unfortunately the values aren't only used for VIEW so I couldn't use them as the identifier - at the moment the Summary field has VIEW in it - in the future this may change but for now i'm happy to have this in the rule :-)

Welcome!

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

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud