How to loop through the lookup results and link each issue to some other, per criteria

[Inna S]

Hi, 

we are doing a migration of the large data set and need to link some issues. 

Unfortunately the trigger 'issue created' used to link every newly created issue to an existing one matching a criteria, hit the throttling limit and can't be used.

I was thinking of making a different automation, that would

- look up all the issues matching a criteria (e.g. no link of specific type is present or a field is empty)

- for every issue in the lookup result, create a link between the 'current' issue in the loop and the one with the one field value matching field value in the 'current' issue.

I'm having trouble iterating over the lookup results: added Log step to print the issue key but this doe not work as expected.

I then can't seem to find the way to link two issues when one of them is 

- not the trigger issue

- not a recently created issue

Is there a way to link just two arbitrary issues or full the system into treating the lookup result as a triggerIssue of a kind?

Thank you!

[Alexey Matveev]

Hello,

I guess, your question means that this group of users has also access to projects, to which they do not have to have access. It means that the users in the group are also included in other groups or roles and these groups or roles have the Browse Issues permission in the projects where the users should not see issues.

You should remove the users from such groups and roles or remove these groups and roles from the project permission scheme of projects, which must not be seen by the users.

[Alain Goodarzi]

Thank you, As I mentioned I need to training resource, what is your suggestion?

[Alexey Matveev]

You can find more info here:

https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

[Joe Pitt]

JIRA works by GRANTING access. You can't restrict access. By default it grants access to the group used to logon (used to be jira-users but may be different on your version).  This is probably where you're getting the access from.

 The FIRST thing you need to do to get control is to remove any groups with logon privileges from the permission scheme unless you absolutely want everyone to have that permission.  Then I suggest you setup user roles for the various functions like, tester, QA, Browse Only, etc. Then you can create one permission scheme to cover almost all projects. The project admin controls which users are put in the roles.  This may be a big effort, but it will payoff down the road by making it easy to control access.

[Alain Goodarzi]

Thank you for your answer.

What is your document, tutorial or book suggestion to be able to follow how to do these. I have searched a lot and bought two training courses but main problem is they are out dated versions and menus are different and their contents are basic.

[Grigory Salnikov]

Hi!

You should try to set issue security level and use "Current Assignee" option. I think that will do the trick.

[Yogesh Mude]

HI @Alain Goodarzi

If you want to limit them to have access to their project and issues only then add the group and reporter to Browse project permission.