|Type||The requirement management system type (JIRA, DTP, etc.).|
|Server||The requirement management system URL.|
|Project||The project for which you want to gather requirements.|
A flow must be set up with the correct server/credentials for the artifact to function properly. In order to demonstrate how to configure the flow, we will use the JIRA example. The flow specifies how to connect to JIRA, including authentication, and how to transform the response into the appropriate format. If you are working with JIRA, you can customize this flow to suit your JIRA implementation. If you are working with a different requirement management system, you can create a similar flow for that system.
By default, the flow limits the queried results to 1000 items. You can change this limit by setting
parameter to a greater value in the Endpoint field of the JIRA Query node.
parameter can be customized to add any valid JIRA JQL parameter, but make sure that the JQL parameter value is HTML escaped. To pass the following JQL parameters, for example:
will be automatically replaced by the flow, you need to set the following (after URL encoding):
The Get JIRA Story node transforms the JIRA API response into the expected format.
You can customize the expected payload to suit your JIRA system details. For other systems or custom implementations, use a function node with
property using the following format as a guide, as well as an HTTP Request node similar to the one shown above.
This artifact can be used to create two widgets: