i have an issue, currently i need field cascading more than one, it possible or from out there has add-on for this?
or maybe to add on the fly field.
I need 3 different cascading to show like below when created the issue.
Prod-1 | Open
Prod-2 | Closed
Prod-3 | Open
I really appreciate for suggestion or feedback.
Sorry I'm not sure about what you intend to do, but if you want to dynamically add elements into a Cascading Select field using a post-function (maybe this is what you mean by "on the fly"), you can do it using "Add a new option to a Cascading Select" post-function, provided by JIRA Workflow Toolbox add-on.
Hi Armario, from post-function is not what I want.
example : when I created the issue(still on create screen), I can add customField"Country", customField"Town" as one group and I can add as many as I want on screen.
*sorry for my English
I know as default JIRA not support my required, but what I want to know is, "there is a solution out there to accommodate my required?"
maybe used some script or need create an addon, or maybe not have solution.
Currently I create a 10 field and show only first, and another will trigger by field value.
If a first field has value, the second field will appear. if the second field has a value a third field will appear and so on. but I think is not efficient.
that's why I need help for another solution like "add as many as I want".
Sorry, I should have expanded on "no custom fields". There are none in the core product, and none that I can find in the marketplace.
You could try the table-grid editor add-on as it's got some related functions, but that's not quite what you're asking for.
btw, thank you for your comment,
on-the-fly means, I can add dynamic cascading group on create screen.
I have cascading value :
then on create screen I want to add like below:
and on the edit screen i can change like below:
Sorry Ryno, but I don't understand what you intend to do. Cascading Select custom fields allows you to create a 2-levels hierarchy of values. When you select a value for first level, you are automatically resticting the available values for the second level.
That hierarchy is defined for each custom field and context. The context is defined for issue types and/or project. This way you can define different hierarchies depending on the issue type or the project where the field is used.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot