Hey i am facing a probable permissions issue and i am just wondering a way around it. As it seems, linking issues does not seem to work the way i want it. here is the scenario:
ProjectA has an issue created. As part of that issues workflow, i have created a workflow transition that when clicked, generates issues in other projects on the site (projectB).
So a tech goes to create an issue on projectA, and populates one of my trigger fields. The workflow runs, checks the field, and creates an issue in projectB with the content of the field as the summary.
This all works fine, however when i go back to the issue in projectA, as a service desk rep on the issue, i cannot see the links for those other issues in the projectB site.
As a system administrator I can see the links fine, and they are created by the workflow in the SYSTEM user (another system administrator).
So i think this is a permissions issue, possibly with the browse project permissions. But i would hate to give my users on one project browse permissions on the entire other project. The user who creates the issue is also named either as a 'reporter' or "request participant" on the newly created issue in projectB, so shouldn't they have visibility of links anyway? if they browse to the issue manually, it is created and they can view it. Just the link does not appear for them, which is the nicest point of this system i am designing.
bug, or as designed?
