Cannot synchronize issues with priorities

General Questions
, , ,
1

Originally asked by Support on 21 March 2023 (original question)

Hi,
After change Jira priorities from default:
High, Medium, Low, Lowest to Critical-P1,Major-P2,Minor-P3,Low-P4 we have a lot of problems with synchronizing issues.
Both Jira instances have same priorities (there aren’t any typo), same icon, same name, same color.
The error says: The priority selected is invalid.: priority.

I can’t generate logs from Exalate on this instance, as I’m receiving error.
I tried to add extra code for incoming connection for both Jiras, but it doesn’t work

def priorityMapping = [
// remote side priority <-> local side priority
"Critical-P1" : "Critical-P1",
"Major-P2" : "Major-P2",
"Minor-P3" : "Minor-P3",
"Low-P4" : "Low-P4"
]
def priorityName = priorityMapping[replica.priority?.name] ?: "Minor-P3"
issue.priority = nodeHelper.getPriority(priorityName)

Can Exalate uses different default priorities?

2

Answer by Richard K on 12 July 2023

Hi,

we have only two priorities (catastrophy and none). None is the default.

We sync two Jira cloud instances.

This works for us:

Outgoing
replica.priority = issue.priority

Incoming

def defaultPriority = nodeHelper.getPriority(“None”)
issue.priority = nodeHelper.getPriority(replica.priority?.name) ?: defaultPriority

So we don’t use mapping.

I hope it helped.

Best regards,

Richard