My Requirment is as follows:
Step 2 can be any field which should allow me to set Issue type based on its selection.
Field "Component" have XX, YY, ZZ in it.
On selecting XX, Issue Type should populate only Issue Type A & B.
On selecting YY, Issue Type should populate only Issue Type A, C and D.
Let me know if there is any way to implement such option in JIRA.
No. The heirarchy is wrong - it's Project, then Issue, then component, with the component list being determined at a project level.
In fact, you might be better off doing some more analysis on your usage - it sounds like your components could be projects or issue types, rather than components.
In a way, what you said is right about componenet could be project and is the same idea I told them.
But stakeholder want to have single project instead of having 4 different projects. Due to this requirement, I am searching for way to link Component with Issue type selections.
It's always worth asking.
There is no choice here - before you can select a component for something, you MUST tell Jira the project and issue type.
Actually, you need only the project to select a component. But you are right, the design doesn't seem right and even if you can achive this by custom development, it is worth reconsidering.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs