nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to link multiple different components and link them to forms individually?

Xihao Wang

Is it possible to link multiple different components to different forms individually?

Right now, I see whatever is in the component field can link to any customized form, but I can't choose individual component in the component list to link to the form

Accepted answers

Joseph Chung Yin

@Xihao Wang -

Can you clarify on what you mean by "Forms"? Are you referring to the FORMS functionality provided by the application where one create the FORMs configuration, mapping the FORMS elements to existing Jira fields, and then incorporate the FORMs into the REQUEST TYPE setup or using the FORMS setup to create the issues?

If you are using FORMS setup against specific REQUEST TYPE case creation, then you can create automation rules to trigger off from "Issue Created" event, and then use "Edit Issue" action to control the component(s) tagging for your issues.

Hope this helps.

Best, Joseph Chung Yin

Xihao Wang

Hi Joseph

When I say forms, I mean in jira service desk, there is a form section where you can create your own. When I tried to link a form field to a component field, it shows everything I created in the component field without choosing which one goes into the form. This is fine for one form, however, I have 3 different forms where I have to choose which components goes into the form. Right now, the component field gives me everything that is listed in the component section or nothing. The reason I am doing this way because customers will choose the component and I created the automation to route to specific assignee based on the component they choose.

Does this clarify your question?

All comments

Joseph Chung Yin

@Xihao Wang -

Hope this helps.

Best, Joseph Chung Yin

Xihao Wang

Hi Joseph

Does this clarify your question?

Joseph Chung Yin

@Xihao Wang

First of all, by default when you configure your component setup for your project, you can setup default assignee by using the Component Lead setup. This works will if your users only select just one component for his/her Form submission for issue creation. So you don't need separate automation rule to set default issue assignee in this case.

Secondly, if you have multiple FORMs for your different Request Types issue creation, you can use automation rule to set the component value by using the Issue Created trigger and then use Edit Issue action base on conditions. This way you don't need to include the FORM element which maps to the Component/s field in your FORM's configuration.

Unfortunately, there is no functionality currently for one to design the FORMs setup when mapping to the Component/s field to default a specific component from your project.

Hope this helps. You can just reply back of this response instead of using "Suggest an answer" area to post your reply.

Best, Joseph

Yong Yang

Hi @Xihao Wang

看起来你的目的是根据客户选择的不同 Components 字段值，自动分配工单给对应的 Agents 或 Assignees。Component 自带了自动分配功能，如你的判断条件比较复杂，原生 Component 配置无法实现，那么可以使用 Jira 自动化实现。

至于你提到的在当个 JSM Project 三个表单中引入 Component 字段，下拉列表选项没法定制。从我的经验看，这个问题可能不是关键问题。即使有冗余，客户可以通过关键字搜索或直接选择来找到自己所需 Component。

希望这个回答对你有帮组。

Thanks

YY Bro, 填空题咨询

Ashok Shembde

Hi @Xihao Wang

I have mentioned a few steps for this issue below, please review and check them.

Steps to Associate Forms with Components:

Create Custom Fields: Add a dropdown or a field that allows users to select components.
Set Up Automation: Use Jira automation to associate the correct form based on the component selection.

Xihao Wang

好的，谢谢你的回答.　我其实希望在component可以分类，既然JSM目前没有这个功能。

这个答案目前可以接受。希望以后他们可以增加这个功能

Xihao Wang

I don't think you understand my question. To simplify, I want to categorize component function so I can link them to different forms based on the catagory in the component field. As of right now, there is no way to do that. I will figure out another work around

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management