Hello community,
we are using Jira cloud in my company. In the create issue tab, i would like to add a condition over two fields making them dependent on each other with defined rules : for instance i have field1 and field2, i want something like this : field1 = SomeCountry -> field2 = [options Based on that country]
Thanks
Hi @DADSI Haitam Instead of putting any condition, it's better to use Cascading field.
I would also go with the suggestion here by @Vikrant Yadav @as the cascading field achieves exactly what you described.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Cool, glad to hear that helps. Let me know if you have any follow up concerns. If this answer solved your issue, please click the checkmark to the left of my answer to accept this answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Vikrant Yadav , i checked the idea with one of our Jira administrators and he said that our fields are already being used in a lot of workflows, and changing fileds type may result in Data loss (he wasn't sure about this), so what do you think about this, is it true? and in case of it being true are there alternatives, Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@DADSI Haitam Changing is not possible. It's better to create new cascading field and add in the project. Once field added in the project, then add values to new field for old issues using bulk operation if so many issue or some issue is in then project then do it manually. Once you did the changes in older issue then remove the field which is currently added in the project and keep the new cascading field only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Vikrant Yadav as i've just been told, the problem that one of the admins had encoutered before actually is that cascading fields aren't availabe in Timesheets reportings
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@DADSI Haitam Cascading field is best suits for your request. For timesheet i am not sure, which field supported by timesheet reporting or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.