How can I automate sync'd/duplicate tickets in separate projects?

[Juan Valdez]

Hi folks,

I'm looking for a way to automatically generate linked tickets across multiple projects.

Context:
My user base works with external contractors from a number of companies in a variety of very sensitive projects. We've setup issue security, but using issue / project permission security alone to manage access to the projects seems unsustainable. Currently, we've set the issue security so that the users are organized by their parent company. We also use Active Directory to manage our internal users, but do to our SSO requirements, we cannot add external users to our AD environment.

Sometimes folks from different ext. groups need access to the same issue, meaning that we have to create a paired group. If companies A and B need access, we need a new issue security level that enables access for companies A + B. If a third company C requires access, then yet another issue security level (A+B+C) is necessary. As we bring in more external contractor groups, if we stay with issue security alone, we'll have an exponential number of issue-security groups. This seems unsustainable for both our admin team as well as our users. (side note, we'd love the feature to be able to select multiple levels of issue security—that'd solve this whole problem quick.)

My company's legal team has vetoed "blanket" security levels such as a three-tier issue security system (e.g. top secret, classified, open) due to the wide range of our IP concerns.

This leaves me trying to find a way to manage issue security, project permissions, and user management that is easy for my users, secure, and selective about security.

Request:
What I'm thinking is that we could create a project for each external contractor group (so as to easily manage the security risk) then link issues from my internal users' groups into the external contractor projects. Manually, this isn't that complicated. Create internal project issue, create issue in the contractor project, then link them. However, if my users are creating hundreds of issues a month that need ext. contractors support, this will take a lot of time and management from my internal users.

I'd like to utilize a workflow in the internal users' projects that automatically generates child tickets in the external contractor projects (not the "parent" internal project), then links them, and can update the status of the workflow of either linked issue, should the issue move. Has anyone created something like this before?

[Vladimir Taranchenko]

Sorry, it was case for Server, not Cloud.

Here you can find variant for Cloud 

https://community.atlassian.com/t5/Jira-questions/Issue-Transition-in-Jira-Cloud-ScriptRunner/qaq-p/850667

[Vladimir Taranchenko]

Hi!

Creation isn't main problem. Synhroomize changes in issues look like some more interesting thing. It's analitical task. Create issue, link it and update by parent's event aren't big problem with Groovy script. What type of help you need?

[Juan Valdez]

I've got little scripting experience, but I'm willing to learn. This still the most up to date documentation for Groovy? https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/component/ComponentAccessor.html

The goal would be to "sync" an issue across two or more projects. By "sync" I mean linking two issues in different projects so they progress / regress along identical workflows. Example:

If the workflow looked like:

Submitted -> In Review -> In Progress -> Complete

And one of these "sync'd" issues was created, if I moved issue A in project A from Submitted to In Review, then issue B in project B would also automatically move to In Review. In this way, we could give external contractors the ability to interact with the workflow status issues in other projects that they don't have permissions to access.

[Vladimir Taranchenko]

Lasted API

https://docs.atlassian.com/software/jira/docs/api/latest/

Use 

https://docs.atlassian.com/software/jira/docs/api/8.2.6/com/atlassian/jira/bc/issue/IssueService.html

 def transitionValidationResult = issueService.validateTransition(user, id, transitionId, issueInputParameters, transitionOptions)
if (transitionValidationResult.isValid()) {
def transitionResult = issueService.transition(user, transitionValidationResult)
if (!transitionResult.isValid()) {
log.warn "${transitionResult.errorCollection}"
}
} else {
log.warn "${transitionValidationResult.errorCollection}"
}