We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 57
    • 4
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      It would be great if the request type groups were also exposed to the search filters and/or JQL. Specifically the use case here is when you want to have a singular service desk entry point but issues created from it are isolated to individual agile boards for segmented teams.

      At the moment the only way to do this is to create many "duplicate" request types that map to an issue type for workflow and group for display then have the board filter against the various (sequential variations, e.g. request-name and request-name2) request type names you might need. This of course can be managed with some level of accepting duplicates on the request type and the expectation that any time those change the filter for the board will need to change.

        1. cust_request_type_group.png
          51 kB
          Aaron St.George

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 57
              • 4
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

                It would be great if the request type groups were also exposed to the search filters and/or JQL. Specifically the use case here is when you want to have a singular service desk entry point but issues created from it are isolated to individual agile boards for segmented teams.

                At the moment the only way to do this is to create many "duplicate" request types that map to an issue type for workflow and group for display then have the board filter against the various (sequential variations, e.g. request-name and request-name2) request type names you might need. This of course can be managed with some level of accepting duplicates on the request type and the expectation that any time those change the filter for the board will need to change.

                  1. cust_request_type_group.png
                    51 kB
                    Aaron St.George

                        a620038e6229 Jehan Gonsalkorale
                        68261b51a40f Aaron St.George
                        Votes:
                        190 Vote for this issue
                        Watchers:
                        101 Start watching this issue

                          Created:
                          Updated:

                            a620038e6229 Jehan Gonsalkorale
                            68261b51a40f Aaron St.George
                            Votes:
                            190 Vote for this issue
                            Watchers:
                            101 Start watching this issue

                              Created:
                              Updated: