The author of the issue does not see the related task

[Игорь Титов]

I have an automation rule that creates a related issue in another project.

I see this connection block in the issue, I am the admin.

But my colleague does not see it.

He is in the "Project managers" group. And he is the author of the Parent issue. 

I gave him the rights to the issue through the "Project Role". But it doesn't help. 

[Tessa Tuteleers · Accepted solution]

Hey @Игорь Титов , 

If he searched for the FD-1783 issue itself, can the user find it? (i.e. it is not that he doesn't see the "linked issues" widget in the original issue, but simply doesn't have access to the FD issue itself.

The user will need "Browse project" permissions in the FD project as well, to see issues in that project, can you confirm that the user has this permission? 

You can easily check why the issue isn't visible to him by going into the FD project -> project settings -> permissions -> permission helper. 

That will tell you whether he is in the right group or role to have browse project permissions. 

Hope this helps, 

Tessa

[Игорь Титов]

Oh! I get it. 

I understood that in order for a user to see the status of a related issue from the FD project, he must have access to the FD project.

I have to grant him access in the FD project to the "Browse project" option, right?

But what if the user should not see all the issues from the FD project?

He should only have access to his created issue. If I give access to the "Browse project", he will also be able to see all the issues of the FD project.

[Tessa Tuteleers]

Hey @Игорь Титов

That's right!

Is your automation creating the issue with the original user as the reporter?

You can give Browse project rights to the reporter field as well, that way you will only see the issues in that project if you are reporter. 

If the issue is created under a generic user (e.g. The automation for Jira user), you can have the automation rule fill in the original user in a different custom user field (e.g. "Original reporter " or something) and set browse permissions on that field.

You should be aware that if you set browse project permissions to a custom field, the name of the project will become visible to all users of your instance on the project overview page (everyone sees the project, but most likely no issues because they are not in the field anywhere). 

Hope it helps! 

[Игорь Титов]

I didn't understand exactly how I should add users to automation. 

For example, I have 5 users who have permission to create parent issues in project A - the automation rule "for creating issues in project FD" works in this project.

How it should work:
1. User #1 creates an issue in project A.
2. The automation rule in project A creates an issue in project FD.
3. The automation rule must be executed on behalf of user #1.
4. User #1 should have access to the created issue from the FD project, but should not see all other tasks.

Similarly, the rule should work for users 2, 3, 4 and 5

[Игорь Титов]

Its ok! 

its works as you said )) 

[Игорь Титов]

thank you very much ! 

[Tessa Tuteleers]

Woops, didn't get the time to respond :) glad you got it working @Игорь Титов