Automation for jira sever can't find project

[Druvis Vilcāns]

Hello, I have problem with automation for jira server.

When I try to make new rule I get please select valid project error.

what to do?

[John Funk · Accepted solution]

Hi Druvis - Have you check the Permission Scheme for that project to be sure you have at least Browse Project or Administer Project permissions for that project? 

Do you get it for all projects? Or just a particular one?

[Druvis Vilcāns]

Hi John, I am jira administrator and I have administration permissions in project.

Error shows up when I try to change anything in existing rules, like assignee.

Rules are defined as followed: 

When Epic is created by reporter, then add new task to the {Same project/Current project/Specific project} with link to parrent epic

[John Funk]

Ah, is this a Next-gen project?

[Druvis Vilcāns]

I am using JIRA Software server, so I don't have Next gen projects

[John Funk]

Gotcha - forgot to check that. Next-gen projects have an issue for Automation for Jira for Epic Links.

Can you post a screenshot of what the rule looks like right now?

[Druvis Vilcāns]

@John Funk 

I made new permission scheme - copy from previous and assigned it. 

And then it started to work, like it should :?

[Druvis Vilcāns]

So thank you for idea, to replace permission scheme - will check what was wrong in logs. :D

[John Funk]

You can try it and see  :-)

[serge calderara]

@Druvis Vilcāns did you solve your issue, I have exactly the same behaviour.

I have a running set of rules for Project A that I need to copy and adjust for a Project B.

For that I simply export/import the running rules to from A to B.

Then what is happening, is that even with full admin rights, I am not able to enable the rule in project B and when I try to edit it, I get the error please "select a valid project" and I am 100% sure that the project is valid as it appears on the drop down sleection list.

Any idea how to solved ?

regards

[Druvis Vilcāns]

Hello @serge calderara

Try changing permission schema, for me it worked, but in my case I just copied permission scheme, and it worked.

regards Druvis 

[serge calderara]

Hello @Druvis Vilcāns  and @John Funk I have try that already from your description by recopiing the whole permission scheme of running project and associate to new one.

By doing so it does not help, what ever the rules I copied I get same error (even if I am full admin) :

[Druvis Vilcāns]

@serge calderara  can you post both permission schemas, for both projects?  

[serge calderara]

dear @Druvis Vilcāns , I find out something new.

I simply edit the permission scheme to trig a change, then set back the changed permmission and it start to work...

really wierd case :-(