Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to configure JIRA component in Agile Workbench

SA-55783

Summary



Unable to configure JIRA component during integration with Agile Workbench.


Error Messages



Not Applicable


Steps to Reproduce

  1. Follow the instructions listed in this article: Integrating Agile Workbench with JIRA
  2. While configuring Integration on the Integration & security tab of the Application rule form, select Configure Integration.
  3. Choose Jira. Click next.
  4. Enter the URL for the on-prem install of Jira.
  5. Click next. No projects display in the dropdown list for projects.


Root Cause



expand=issueTypes is not supported for the on-prem version of JIRA. Agile Studio fetches all the projects along with all issueTypes (Bug, Story etc.) expanded in a single REST call to JIRA and then iterates over all the projects. Only the projects with stories and bugs are valid projects considered for integration with Agile Workbench. 

Resolution



Perform the following local-change:

If the REST call for list of projects along with expand=issueTypes does not return any issueType in the response, Agile Sudio does not assume the project is an invalid entity for the project list. Initiate another REST call for all such projects individually and obtain the information on the project. JIRA’s GETProject API returns the project’s information along with issueTypes when query is fired for individual projects.
If the response from JIRA contains Bugs and Stories, consider those project as valid and add them to the data page that is the source of the project dropdown.

Published August 24, 2018 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us