-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
4
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
When having multiple JIRA instances and you want to have your issue updated based on an remote linked issue, you want to receive a notification back in your original issue.
- duplicates
-
JSDSERVER-5246 Ability to automate an issue when a linked issue from a linked instance is transitioned
- Gathering Interest
- relates to
-
JSDCLOUD-4773 Automation rules to work with remote issue links
- Gathering Interest
- links to
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
[JSDSERVER-4773] Automation rules to work with remote issue links
Support reference count | Original: 3 | New: 4 |
Labels | New: ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 980974 ] |
UIS | Original: 3 | New: 2 |
UIS | Original: 6 | New: 3 |
UIS | Original: 3 | New: 6 |
UIS | Original: 6 | New: 3 |
UIS | Original: 3 | New: 6 |
UIS | Original: 2 | New: 3 |
Yes we have the following scenario which we can't account for in Jira cloud because the automaton rule doesn't support it
so it would be great to see this implemented where we have a remote link created trigger with smart variables also available for remote links and their info such as url, name