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

Create JIRA issue with watchers (confiForms)

Michael Küng

Hey everybody,

I am facing some problems to add watchers during the creation of a JIRA issue by using the IFTTT from confiforms (v3.4.3).

It was running properly in the past, but now it seems not working anymore. I tried to use different kind of values in the "Watchers" field, e.g. username, fullName, e-mail. Nothing works anymore. In the past it works with the username (kuengmi in my case).

Anyone else facing some problems?

Accepted answers

Alex Medved _ConfiForms_

You need to have the same usernames in your Jira and in your Confluence and a username is expected when adding watchers to the issue

Alex

All comments

Alex Medved _ConfiForms_

You need to have the same usernames in your Jira and in your Confluence and a username is expected when adding watchers to the issue

Alex

Michael Küng

Thanks for the fast answer Alex.

I know, but also if I add the usernames manually to the field watchers, like e.g. kuengmi it wont work.

Is this error also connected to the switch to AzureAD, like you work on SUPPORT-5083?

What I don't understand why is it working with Assignee/Reporter, if we using the username which are stored now in a cup.field. I would expect if we have problems by the change to AzureAD, also Assignee/Reporter should make problems.

The code below is still working...

If I try the following it wont work....

But where is the difference to Assignee/Reporter? Alle three fields refer to a user field, where the content where changed by the change to AzureAD, only watch don't work anymore if we refer to cup.field-7.

JIRA users:

Sorry for the bad explanation

Michael Küng

A colleague tested it via REST API and it works, the problem is related to the IFTTT via confiForms...

Alex Medved _ConfiForms_

How can this be related to ConfiForms only, if ConfiForms uses REST APIs to communicate with Jira!?

And things were working until the recent change with a switch to AzureAD (you have mentioned a private ticket we have in the queue SUPPORT-5083)

Alex

Welcome!

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

Quick Links

Find more posts tagged with

confluence

server

confluence-server

jira

confiforms