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

Scriptrunner Behaviour mapping issues

Michele Ghirxi

Hi,

I was testing some functionality with regards to behaviours and came across what seems to be unintended behaviour.

I have two projects, Project A and Project B (Completely fresh projects). I created a behaviour which is mapped to Project A. All the behaviour does is set the priority field as read-only.

When going to create the issue on Project A, the 'priority' field is set to read-only, which is what I want to happen.

When I switch to Project B, the field is not set as read-only, however after clicking create it is set to read-only when it shouldn't be. It seems that it's carrying the behaviour over from Project A.

Has anyone encountered this behaviour before?

Accepted answers

All comments

Lih Yao Tiong

Hi @Michele Ghirxi

Please correct me if I'm wrong:

Based on what I observed on the screenshot you attached, I noticed you only mapping the Behaviour to "Test Project One" Only.

This might be the reason read-only is not working on the project TPT Priority's field.

If you wish to apply the Behaviour to another project, could you please map the Behaviour to the other project/ select All Project while add mapping and see if it works?