-
Type:
New Feature
-
Status: Done (View Workflow)
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: 5.7.0.1-p5
-
Fix Version/s: 6.1.0
-
Component/s: Behaviours
-
Labels:None
-
Sprint:SR4J Sprint 78
-
Critical Points:1
Rather than create numerous SD mappings for a series of minimally-differing behaviours, customers should have a convenient means to access the request type and portal of an issue programmatically, across both server-side scripts and initialisers.
- is duplicated by
-
SRJIRA-4028 Access Request Type name from within Behaviour Scripts
-
- Done
-