|Scroll Table Layout|
|Model name||The model should be named JIRA. This is the default name of the model.|
The profile name must match the name specified in the Profile Search node when you configure the flow. See Flow Configuration.
|DTP Project||The DTP Project that the profile belongs to. If you do not want to associate the flow with specific DTP projects, you can delete the search parameter from the Model Settings node. See Flow Configuration.|
|JIRA Project Key||JIRA Project key (use SP for Sample Project).|
|Normally, the key is defined along with a JIRA ID/issue number. For example, if the project key is Sample Project and the JIRA issue number is 1234, you would enter SP-1234.|
|JIRA Component||Name of the JIRA component for the issue.|
|Issue Type||Bug and Task are currently supported.|
|Closed Status||The flow attempts to transition a Bug to this status when the corresponding violation is fixed.|
|Default Priority||The priority set for all new Tasks, as well as new Bugs with violations that don't match the profile model.|
All predefined values like Issue Type or Status are case sensitive. Please be sure to specify the correct case.
- Double click the node and edit the Configuration field.
When the configuration panel opens, specific specifiy the JIRA server and credentials and click Add.
Info title Create a Dedicated JIRA User for Extension Designer
If JIRA detects that a user is making requests from multiple machines, it may lock the user out. We recommend creating a dedicated user for Extension Designer to avoid being locked out by JIRA.
- Click Done when panel closes and repeat for the other HTTP Request nodes.