Question

Agile Workbench Jira Integration with Custom Priorities

I'm trying to extend the Jira integration with Agile Workbench to include 7 custom priorities, instead of the 5 supported out of the box.

I updated the “SetSeverityFromJira” Decision Table to map the Jira Priority IDs to the Jira Priority Field values in the Pega-Agile-Work class. I'm attaching a screenshot for your reference.

I also extended several of the sections to include the additional priority values, such as pyUserStoryRowExtension, pyBugRowExtension, and JiraStarPriority and set the appropriate Star ratings/priority values in the data transforms within those sections.

So now I can create a new user story in Agile Workbench - and I see my 7 priority values there that I can select from. But if I select the 6th or 7th custom priority value and Save the user story, it reverts it back to the 1st priority value - and won't send that new user story back to Jira.

I looked through the Activities and Data Transforms and I didn't see anything obvious in terms of what I need to update to extend the integration to include the 2 new priorities.

Do I need to extend the 'GetPriorityForJira' Decision Table in the Pega-Agile-Work-UserStory class also? Is that passing the priority back to Jira? I only see 3 priority values there currently, so I'm not clear if that's the same "Priority" or something different.

Do you have any input to help?

Thanks.

***Edited by Moderator: Pallavi to update platform capability tags***

Correct Answer
March 22, 2019 - 5:41pm

Thank you.  I was able to get this working in my 8.1 environment.

Here is a high level overview on the steps to ensure the integration works, when the Jira IDs are custom (i.e. not 1 through 5):  

  • Update 'SetSeverityfromJira' Decision Table with Jira IDs
  • Update 'GetPriorityForJira' decision tables in both the User Story and Bug class with Jira IDs
  • Do a ‘Save As’ on the 'GetPriorityForJira' decision table above in the Pega-Agile-Work-UserStory class.  Give it a new name and change the Applies to Class to “Embed-ProjectMgmt-Pagedata” and map the Priorities to your custom Jira IDs.  Also, click on the Priority column in the decision table and change the Property to:  .JiraFields.JiraPriority.JiraID
  • Edit Activity 'UpdateJiraIssue' in the Pega-Agile-Work class to change the Decision Table Name in Step 5 to be the new Decision Table you updated in the Step above.

Comments

Keep up to date on this post and subscribe to comments

Pega
March 6, 2019 - 10:38am

We do not support the custom priorities with JIRA integration reference implementation of the component on Pega exchange. But seems like you extended many rules to make this happen and can get onto a call for 30 minutes to go over this if needed.

What is your platform version and JIRA component version that you are trying?

Pega
March 7, 2019 - 8:10am
Response to vitts1

@vitts1 - thank you.

I think part of my issue is related to the post here, so I submitted a follow up question in response:  

https://community1.pega.com/community/pega-support/question/jira-pega-workbench-integration-priority-issue?comment-cid=813681#comment-813681

It's not clear to me which rule(s) to update to ensure that the Jira priority is set properly - when the ID is something other than 1 through 5.  Do you have any insight?  Thanks again.  

Pega
March 22, 2019 - 5:41pm
Response to vitts1

Thank you.  I was able to get this working in my 8.1 environment.

Here is a high level overview on the steps to ensure the integration works, when the Jira IDs are custom (i.e. not 1 through 5):  

  • Update 'SetSeverityfromJira' Decision Table with Jira IDs
  • Update 'GetPriorityForJira' decision tables in both the User Story and Bug class with Jira IDs
  • Do a ‘Save As’ on the 'GetPriorityForJira' decision table above in the Pega-Agile-Work-UserStory class.  Give it a new name and change the Applies to Class to “Embed-ProjectMgmt-Pagedata” and map the Priorities to your custom Jira IDs.  Also, click on the Priority column in the decision table and change the Property to:  .JiraFields.JiraPriority.JiraID
  • Edit Activity 'UpdateJiraIssue' in the Pega-Agile-Work class to change the Decision Table Name in Step 5 to be the new Decision Table you updated in the Step above.

March 6, 2019 - 1:26pm

Hi @morak!

I submitted this as an enhancement for you for future consideration. The FDBK ID has been added to your original post. You can view this in our internal system.

Marissa | Community Moderator | Pegasystems Inc.