Using a Typeahead (project) field to pull in correlating issues from a separate workflow/request queue. | Community
Skip to main content
O
OmahaOmaha
Level 4
October 7, 2024
Question

Using a Typeahead (project) field to pull in correlating issues from a separate workflow/request queue.

  • October 7, 2024
  • 1 reply
  • 709 views

Hi All,  I have a question.  Is it possible to use a project typeahead field on a request form, to tie that request/issue to an active project from a different workstream?  In theory I would have a report in the project left panel, that would capture all issues/requests that are tethered to this project via the project typeahead field that was entered on the related issue. The filter on the report would  use the logic that only display issues that have a project typeahead field that matches the project name. Hopefully from this, I would be able to display the selected fields from those issues in this report.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Sven-iX
Community Advisor
Sven-iXCommunity Advisor
Community Advisor
October 8, 2024

Hi @omahaomaha 

 

yes-no 🙂 

So in general: A project can have multiple resolvables, so you can indeed have a project that resolves several issues/requests. 

 

And yes you can create a typeahead that lists projects. 

 

However, the actual "resolve" fields you cannot add as form elements. You need Fusion (or an API call) that picks up the projectID from the typeahead, and sets 2 fields on that request: 

  1. Resolving Object Type = PROJ
  2. Resolving Object ID = {the projectID from the typeahead}
O
OmahaOmahaAuthor
Level 4
October 9, 2024

Ok, with those fields attached to the issue, any updates to those issues would be reflected on the report within the project left pannel?  Essentially I'm hoping to use the project report as a centralized location to keep tabs on other requests associated with the project. Instead of having users getting lost in our instance.

 

Terms & ConditionsAccessibility statement

Loading footer...