Bill Sheboy Expert

Hi @Ryan Zaucha Please try using the Advanced Compare Condition, and checking on the smart value: {{issue.epic link}} Best regards, Bill

Hi @Scott Thurston To help the community provide ideas, what problem are you trying to solve? You describe your team is using JIRA sprints, and so is using a Scrum board. When a Scrum team selects work to complete in a sprint, the team is accountable for the completion of the work/meeting the goal, not one individual. The…

Hi sergeev.viacheslav@telestarcom.ru I believe you have an extra spaced before the parenthesis. This worked for me: {{now.plusHours(2)}} By the way, I found more date/time functions for smart values in the JSD documentation: https://support.atlassian.com/jira-service-desk-cloud/docs/smart-values-date-and-time-functions/…

Hi @Thomas Hamacher -- Welcome to the Atlassian Community You seem to be asking two questions: * What is the ordering of issues on the board?* The issues are ordered by the filter, often something like project = myProject ORDER BY Rank. If you use swim lanes, that ordering can be disrupted. * For Kanban, the best way to…

Hi @Isabelle Giegling The Story Point Estimate field does not appear to be accessible yet for Next Gen automation rules. Here is the backlog item for it: https://codebarrel.atlassian.net/browse/AUT-1393 It appears the field can be accessed directly for queries, as noted in this community posting:…

I am glad that worked for you. Would you please mark this question as answered so others can find the solution more quickly? Thanks!

How about putting and ORDER BY clause on your JQL? That will enforce the order of the pulled data and make interpreting the output more predictable as you try to understand what is happening with startAt.

If you learn the answer, such as that your add-on license expired, please post here what you find to help others with a similar issue. And then mark this question as answered so other people can find the solution. Thank you!

Thank you, as your information helps. The color bars to the left of the cards is working correctly. This is what you configure with the Board Settings > Card Colors. Is that correct? Are you instead asking about the color-highlighting of the fields like HDE-23 (green on your board)? If so, that appears to be configured in…

Would you please post an image of what you see when you go to Board Settings? Thanks!

Hi @Lily Tran You appear to be using startAt correctly, as it is the zero-based offset (index of the first record to return). I wonder if something earlier in the URL is parsing incorrectly and so startAt is ignored. Maybe try removing the fields and maxResults to diagnose this piece by piece. Best regards, Bill

Thanks... Now select the ... > Board Settings > Card Color. Then you can select the criteria (colors based on) to select your card colors. Please see the documentation I linked earlier for details on doing this.

Hi @Jackson Esselman Yikes, and... I just searched and this is a known defect: Jira adds an attachment during search using pasted text from Microsoft Excel https://jira.atlassian.com/browse/JRACLOUD-72383 There is a work-around described in the defect. Best regards, Bill

Okay, that is definitely a Classic project. If it was Next-Gen, you could not change the card colors. Can you see the ... at the top right side of the board? If not, check with the project admin to see if they have changed permissions for who has access.

Thanks for explaining that, @Chimena Ijeh I personally do not believe in "best" practices; only better ones. :^) I have found that as teams improve, something that worked earlier could be less helpful later. Please discuss with your team and consider when a practice needs to evolve to support the team. Best regards, Bill

Hi @Puneet Sharma -- Welcome to the Atlassian Community! You cannot do this type of nested query with out-of-the-box JIRA. If you have one of the scripting add-on products from the marketplace, it is possible. As a work-around you can: * Run a query to get your epic list * Export that result list * Grab just the keys, and…

Hi @José Blanco Villalba Looking at this documentation, Priority is not one of the fields supported for lookupIssues: https://support.atlassian.com/jira-software-cloud/docs/automation-actions/ I checked the public suggestion backlogs for JIRA Cloud and Code Barrel, but I could not find any open items to add this field.…

Hi @Jarosław Solecki [Deviniti] Did you notice that the fields not working for you, Components and Fix Version, are both list fields? I did some rule testing and what I saw was: * Components sometimes worked * Fix Version never worked, even when using fixVersion.name to go inside the item * And Labels always worked There…

Hi @Daniel Orlov -- Welcome to the Atlassian Community! If you will regularly need this data and do not want to purchase a scripting add-on, you can implement this yourself using the automation rules with JIRA cloud. For example: * Add a custom field to capture LeadTime (open duration) * Add an automation rule:* Trigger:…

Hi @Regli Núñez -- Welcome to the Atlassian Community! To configure the card colors, you need to have the project admin permission.. Once you have that, you navigate to Board settings > Card Colors. When you say you can't add colors, what are you seeing? Is the option missing or something else? Here is the documentation…

Thank you for that information. In that case, I would recommend submitting a ticket to Atlassian support. As site admin for a standard cloud instance, you should be able to do that here: https://support.atlassian.com/contact/#/

Glad to help. When you hear back from support, please post back here if there are any updates... although, the other defect is 3 years old ;^) Please consider marking this one as answered so others in the community searching can find that there is an open defect on this symptom. Thanks!

Hi! As you are the site admin for a Standard Cloud instance, you can submit a support defect ticket using this link: https://support.atlassian.com/contact/#/ You can provide the other server defect ID, and ask if they want to fix the issue, clone the original ticket for cloud, or create a new one. Then you will get updates…

Thanks for finding that one, @Sofia Quintero Although I am surprised it is marked as minor...One of the primary purposes of a tool such as JIRA is to store information, and this defect seems to impair the validity of and access to the stored information. The defect you linked is for the server version, and you are using…

Hi @Misty Meyers If you are using a Classic project, you can have multiple boards and multiple parallel sprints running independently. That will allow the teams to start/stop sprints on when they are ready. Please see this documentation for more information:…

Hi @Sebastian Ghelerman -- Welcome to the Atlassian Community! What problem are you trying to solve by seeing changes to the story points? And, is this a one-time issue or a long-term one that needs monitoring? I am asking because, as you noted, CHANGED only supports a limited number of fields, so it can be difficult to…

Hi! I am not using any of the requirements management add-on features. You could look in the marketplace to see if any might help you: https://marketplace.atlassian.com/ If you are just using the default levels built into JIRA cloud, creating a single query/report is more difficult due to the manner items are linked,…

Hi @Srihari Melukota -- Welcome to the Atlassian Community! How are you representing 7 deliverable levels in JIRA cloud? With out of the box standard JIRA cloud, you normally only have 3 levels of issues: epic, story or task or bug, and sub-task. If you are using an add-on product to accomplish all of those levels, please…

Hi @Sofia Quintero I searched the public open tickets on this issue and I could not find anything similar to context change causing this symptom. As this does not appear to be status related (which is a known Classic/Next-Gen project "behavior" in duplication of values), I recommend contacting Atlassian to submit a defect…

Thanks, Nick. I meant to try browser zoom to less than 100% to see if appears. There appear to be defects in the UI for JIRA when you have a computer resolution set higher than 100% (such as for high-DPI monitors) or used accessibility functions. That can interact with browser zoom because not all parts of the UI are…