John Funk Community Champion

Hi Marco, You should use the Field Required Validator. 

Hi @[deleted] - I am marking Trudy's answer as accepted. Please let us know if you still need assistance. 

Hi @Johannes - Welcome to the Atlassian Community! You should always start a new question so more people will see it and can help. And answers can be tailored to your specific situation. 

Okay, thanks. It looks like you are trying to rename the default swimlane. You cannot delete that if that's what you are trying to do. There must always be a swimlane that will catch all issues that pass through the other swimlanes based on your board filter. Otherwise, there would be the possibility that issues would…

Hi Abdelhalim - Welcome to the Atlassian Community! If you make the field Required, it will get rid of the "none" option. It will default to the first value in your list, unless you designate a different Default value. 

Hey Antonio, Can you share some more details? Maybe some screenshots? What type of project is this? 

@Summer Hogan - you should have bribed them to let you ride the giraffe! That would have topped everything here so far. 

All signed up. Looking forward to the demo as well. 

Always love to see more integrations and automations. Such huge time savers. 

Haha - yep, I imagine most of use took our dads for a ride when we were little. My boys certainly did that with me!

Hard to beat unicorns and dragons! But horses are certainly a good substitute!

Ah, our first donkey! Never been on one but would certainly give that a try! And yes, I will need to come back here and update with any photos as I get adventurous. Hoping others do the same!

New password for you Dave - CamelRiderDave999!

Well done! Hoping to make it to Morocco later this summer or maybe in the fall. 

I would classify a bull as exotic! And not about to get on one. haha

Excellent! I am hoping to visit Tunisia one day as well. 

True! I don't go horseback riding often, but always enjoy it.

WOW - would love to see a picture of that!

Maybe create a variable to capture the key of the Epic under the Most recently created issue branch. And then use that value to update the Epic Link field of the trigger issue. 

Thinking @Cristina don't live here any more. 

Hi Candice - so sorry it has been this long! Yeah, I don't think you are going to be able to use syntax like that for the second part where you are using the minus. Try using a variable instead of the issue.field name part. https://support.atlassian.com/analytics/docs/date-and-time-functions-for-variables/

You might take a look at this post and see if it can help you. I am able to use code that is references in my automation to pull in form data. * Date Fields: {{issue.properties."proforma.forms.i1".state.answers.AAA.date}}…

Well, one way would be to not populate the Approvers field until someone selects a value for the environment. Then you could have an automation rule that fires on the environment field update which populates the Approvers field. The the user would get the approval email. 

Sorry - you probably should open a support ticket with Atlassian as I am not able to see your data or delve further into it. 

Hi Sayed - Welcome to the Atlassian Community! Those 3 fields must have a value in them to create the issue (they are required). So you need to populate those fields with a value. 

Hi Sam, No, I am not aware of a way to do this while in process of cloning the issue. You can send an email after the issue gets created to update the issue. And you can prevent it from moving forward in the workflow. But not when it is being created. 

Hi Nikhil, There is probably a couple of ways to go about this, but whether I would attempt or not would depends on the number of options available for the Department field. But the thought is that you need a custom number field per Department value such as Motor Count, Engine Count, Tires Count, etc. depending on the…

Looks exciting!

Great - in that case you associate the custom fields to the issue type through the custom fields themselves, and not through the issue types. Go to Settings > Issues > Custom fields and search for the custom field. Then click the 3 dots menu to the right and select Contexts and Default value. Then add the Issue Types for…

Hi Céline - Welcome to the Atlassian Community! How is it failing? What is the error message you are getting? Can you share the audit log for the issue when the rule runs?