2
1
0
1 answer
- 10-1
Hello Harold,
Is this in Jira Cloud or in Jira Data Center? We have got triggers running in Jira Data Center using JQLs with project names and they are able to sync.
We are running on Jira 7.13.2 with Exalate on
Although I have seen something like this pop up in a different issue. Do you have a project whose key is SUPPORT as well as a project named Support?
In these cases Jira will prefer returning results of the project whose key is matching.
Kind regards,
Marcus Nygren
Add your comment...
I have created a new connection and the trigger for that connection does not work when I have a specific AQL for it, meaning, if the trigger is:
everything works well
but if the trigger is:
the trigger does not work and issues are not synced when they need to
yes, I have tested the AQL in Jira and when I run it I do get results as expected.
Hi,
I believe the problem is that you need to use the project key instead of the name of the project, for example
Kind regards,
Harold Cruz