Jovin Community Champion

Hey @suneel babu Thanks for those, by the looks of things in your 3rd screenshot you want to hide "Job Level" is NOT W-2. In that case, you should ONLY select W-2 in the "is any of", as the conditional display dictates when to SHOW not when to HIDE. Currently, your 3rd screenshot will have the section "Hide this field if…

@suneel babu Could you provide a screenshot of the form in the editor so we can troubleshoot?

Hey @suneel babu Good question! You can indeed achieve this. For the conditional display sections they will affect all downstream areas. To have something always display after a conditional section you'll need to add a section and have it always display. Similarly for your nested conditional, it could look like this:…

@Arooba Al Siyabi Great question! With regards to the approvers, it's not the intended use of the Approval step BUT you could: Create a separate user picker field to store the actual approvers in (e.g. "Request Approvers") In the actual approver field only add "Automation for Jira" Create 2 transitions from "Awaiting…

@Pascalle Leeuwerink Absolutely! That's what the community is for, glad I could be of help! Would you mind marking the top level comment from me as "Accept Answer" so others can find this and implement a similar solution if it matched what you hoped to achieve overall?

Hey @Pascalle Leeuwerink You'll need to look at from the perspective of adding customers to the Organizations, rather than Organizations to the customers. You can see the blue "Add Members" option on the Organization, there you can add up to 50 at once. To remove a member from an organization, click the little "Trash Can"…

Hey @Pascalle Leeuwerink The organizations for customers cannot be added as a member of another Organization, but a single user can be added to multiple organizations (e.g. they could be in AMAG and AMAG Basel). If you want to merge two, you'll need to move the members across by adding them all to the correct organization,…

Hey @lenny_zenith Here are few things to check, but are you able to provide some screenshots to help us (can blur the ticket details)? * Check the board you're accessing is a "Sprint" board and not a "Kanban" board* https://support.atlassian.com/jira-software-cloud/docs/switch-between-projects-and-boards/ * Check the…

Hey @Antonia This is a regional setting that I'm not sure can be modified (e.g. US uses '.' for decimal, Europe + others use ','). Perhaps check if your region settings for your profile affect it? https://id.atlassian.com/manage-profile/account-preferences

@Stanislav Borisov No worries then, off the top of my head I would do the following (may not be the best solution, but it'll work): * Create a new custom field "Commented Approvers", this will be a User Multi-Pick field type. It's purpose is to track the approvers that have commented on the issue. * Ensure this new field…

Hey @Stanislav Borisov Let's dive into the process a bit - is there a reason you're looking for a comment from all the Approvers, instead of just clicking the Approve button, and requiring all people in the field to approve?

Hey @Stanislav Borisov Until the approver has approved the issue it won't appear in there. Instead, you should look to see if the user who commented is in the Approvers field (or a group if there is a specific group). For the field you could use the below in your condition: 1st Value: {{issue.Approvers}} Condition:…

Hey @iatkinse To update the Start Date field all you'll need to input in the field there is below: {{now()}} That should help :)

Hey @Christopher Johnston This can be done with the below JQL: resolved = 2025-03-07 This will show all issues resolved on the 7th of March 2025. Is this what you mean? 

Hey @Matt Muldowney Great question - it sounds like you may have created these in "Team Managed Projects" instead of "Company Managed Projects". Good news is, you can definitely do this, but you'll need to create entirely new (Company Managed) projects for the issues to go into. Here are Atlassian's…

Hey @frankie_medina This could be achieved with an automation rule like the below: * Trigger: Issue transitioned* FROM: Leave blank * TO: * Action: Lookup Issues* JQL: assignee = {{initiator}} AND status IN ( ) * Condition: Smart value condition* First value: {{lookupIssues.size}} * Condition: Greater than * Second value:…

Thanks @Dirk Ronsmans Not sure I can add much more value to this than what the others have said - making use of a UUID generator via API could be good, or leveraging a FOR smart values loop to generate the GUID (numeric only) using the random function if you want to stay inside Jira: * Create variable {{guid}} value could…

@Ashley Honeycutt You could create a custom field (short text) called "Creator Time Zone" (or whatever field you're looking at, and have the field populate from a trigger of an automation rule: e.g. to have it auto-populate when the time is filled in (assuming your date time field is called "Issue start" * Trigger: Field…

Hey @Dirk Ronsmans Could you expand on the design of this a little? Some prompting questions and I'll see what I can make of it once answered: * Does the GUID need to match a specific length/pattern/alphanumeric pattern? * Is it likely that a single Jira issue would have more than 1 GUID associated with it during it's…

Hey @Ashley Honeycutt Date Time fields are always displayed in the user's local time based on their profile. They can update their profile accordingly here: https://support.atlassian.com/jira-software-cloud/docs/manage-your-jira-personal-settings/

Hey @Лёня Криволапов There are a couple of ways to achieve this, I'll only cover the one that doesn't involve using APIs and parsing information like that. * Setup a new custom field (you can name it differently):* Date Sold: The date the task entered the sold status * Setup the workflow to populate this information:*…

@Mohamed Saad Taha - can you perhaps expand on your needs with a more thorough example? Such as: I want to be able to prevent a tester from updating the status of a story until the developer has transitioned it into "Ready for Test". I want to make it so only Tech Leads can update the story points of a story after it has…

@Trudy P Claspill I didn't know that one! Learning more every day. Thanks for clarifying this one! @Davi Germano Amorim I'd accept this answer over mine if it solves it for you 🙂

Hey @Davi Germano Amorim In cloud the only way to do this would be to create 2059 issues, then when you import your new issues it will start from 2060. You could do this by importing 2059 "dummy" issues from a CSV and then deleting them all.

Hey @Darshan Hiranandani Great question - you can achieve this through automation rules! You'll use the trigger being a field value updated, then you'll find the issues that are "blocked by" this issue and adjust their start & end dates accordingly. Note: You'll need the rule to have scope for all projects you wish this to…

Hey @suneel babu Rather than using Smart Value condition, try using "Issue field condition" and choosing "Type Of Hire", then you can specify "is not" and choose "Offshore".

Hey @Balaji To see this on issue fields in JSM you'll need to enable the feature in Settings: After this, you can create Organizations and also create fields on them as well. This will allow you to see this information in the right-hand information pane on the issue view. See some documentation on detail fields…

Hey @suneel babu I find the best thing to do when working with forms is to link the fields to Jira fields in the back end. Depending on how you have your first/last name setup you can then do 1 of two things to access this. Option 1 - Two fields On the form create a "First Name" and "Last Name" field, link these to Jira…

Hey @Urmo Unfortunately the email is not stored anywhere on the issue data, so you will not be able to access it like this. If this is a requirement my advice would be one of the two ways: Option 1 - Duplicate your information After each "Send Email" action, create a "Log action" action and have all the same information…

Hey @Amit Kotiger In terms of being able to manage this out of the box, the forms route is a great one. The good thing about the Forms is that even if they're locked, when you update the field in the normal Jira Issue View, the form will show that same updated value if you've linked the fields on it. There are also…