Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Pre conditions for Issues creations on jira cloud

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]


1 answer

1 accepted

Hi @DADSI Haitam  Instead of putting any condition, it's better to use Cascading field. 

Ismael Jimoh Community Leader Apr 22, 2021

I would also go with the suggestion here by @Vikrant Yadav @as the cascading field achieves exactly what you described.

Like # people like this

Thank you guys, i'll try this out and get back to you

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. 

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

@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. 

@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

@DADSI Haitam Cascading field is best suits for your request. For timesheet i am not sure, which field supported by timesheet reporting or not. 

Like DADSI Haitam likes this

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you