HHH Posted June 5, 2017 Posted June 5, 2017 I need some help connecting guest.ui.app.com.hornbill.servicemanager.integration.jira.issueType and guest.ui.app.com.hornbill.servicemanager.integration.jira.projectName to a change ticket since these will be chosen when creating the Jira from within Hornbill. My question is: How do I add this information to the business process since it's dynamic.
AlexTumber Posted June 5, 2017 Posted June 5, 2017 Hi, The 2 application settings you mention here are there to act as a default and to save you entering in the information every time in each bpm node each time you want to create a new Jira request. If you leave the input param on the bpm node to 'Auto', it will look for a value in these settings. You can manually specify the Project Name and Issue Type by selecting them from the drop down menu. If you want to add additional options to the drop down menus, you'll need to add them to the relevant simple list(s). Hope this helps, Alex
HHH Posted June 5, 2017 Author Posted June 5, 2017 I found those but adding those in the setup would not really help since the issue type and project would be set on a per ticket basis by the Service Desk staff creating the Jira ticket.
AlexTumber Posted June 5, 2017 Posted June 5, 2017 Just so I understand correctly, do you need to make the decision in the business process? Something like this maybe:
HHH Posted June 5, 2017 Author Posted June 5, 2017 That would be it, thank you! Edit: What would the "Determine Jira Ticket Type" look like if expanded in order to get the right information for the decision? Right now i get outcome yes/no so I must be setting something wrong. 1
AlexTumber Posted June 5, 2017 Posted June 5, 2017 It can be anything you want it to be. I would use one of the get request information options that sit under the Requests entity then make a decision from there. e.g.
HHH Posted June 7, 2017 Author Posted June 7, 2017 I think we're misunderstanding one another here so I'll rephrase. How do I get the information into the request itself. For example the assigned team gets a drop down where they can choose Bug or Improvement which then leads to the decision. So in your diagram it would be som kind of a human interaction before the "Determine Jira Ticket Type"
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now