setting priority based on an Urgency-Impact matrix not working (scriptrunner behaviour)

[João Filipe Silva]

Hi, 

we're currently having some troubles getting this script to work on our Jira Service Management.

We copied the code into a new behaviour, added it to field priority and created the corresponding service desk mapping to all request types.

All the values used in the script exist for fields Impact, Urgency and Priority.

However the priority always defaults to High. Are we missing something?

edit: we also meet the minimum requirements.

edit 2: By having the priority field visible on the customer portal, we can see that field priority is set to High and can't be changed, even before inputing values for urgency/impact (we double checked and priorities configuration, we have None for default value on our SDM project priority scheme)

[Dave Thomas]

I was hoping to see an answer here because our problem is similar.   We are using the built-in pre-receive hook to to Require commits to be associated with a JIRA issue and it will succeed if it finds a matching Jira issueID in either the commit or in the branch name.   The problem:  if the developer created the branch with the correct Jira issue ID mentioned, they are able to commit without any valid issue ID mentioned at all.  Once the pull request is merged and the branch is deleted, the Jira tracability for these commits is lost.   We're hoping there's a way to either force the hook to only look at the commit messages and not at the branch name or else to do what's mentioned here:  require the issue ID to be mentioned in both the branch name and the corresponding commits.