Bill Sheboy Expert

Hi @Nick Sturge -- Welcome to the Atlassian Community! That is odd... The only time I have seen this before it was a scaling issue. Have you tried adjusting your browser zoom to see if it reappears? Best regards, Bill

Hi @Fernando Giovanini Has your automation rule changed recently? The only other postings I saw similar to this symptom were when invalid special characters were entered in the From Name field (under more options) for sending the email or when the recipient email addresses were not valid. Best regards, Bill

Hi @[deleted] You could do what you are asking with custom fields and the automation rules, which are included with the Cloud version. Please look over these links to learn more information: https://www.atlassian.com/software/jira/guides/expand-jira/automation…

Hi @Lisa Besteni The two tools in JIRA cloud that are intended to support this are the Version Report and the Epic Burndown Report, which you can read more about here: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-version-report/…

Hi @sofia.pedro I apologize for my error: it appears that it is not yet possible to trigger a rule based upon an Epic Link change. Here is the ticket for that issue: https://codebarrel.atlassian.net/browse/AUT-1264 Regarding replacing existing labels, with the edit action you can select the ... to the right of the field…

Hi @Chimena Ijeh You appear to asking a question that depends upon how your team does work. For the community to help, you may need to provide more details. For example... * Some teams consider finding and resolving defects as part of the original request, and so there are no separate work items created * Other teams track…

Thanks for that information, Sofia. How do you select the issues for that gadget: with just one project or with a query? However you do this, I was suggesting using that same selection criteria to check if the values of the custom field are indeed identical, or not. (e.g. "Low" vs "Low ")

Hi @Sofia Quintero When you examine your JQL that you use for this gadget, are the values actually the identical for the custom field, or slightly different (e.g. extra spaces)? You can check that by running the JQL separately in issues and filters and comparing the results. Best regards, Bill

Hi @JOSE SANTIAGO BONILLA PAZMINO I wonder if you are mixing issues about the Scrum framework and what the JIRA tool is capable of supporting... When Scrum notes a potentially shippable product increment, it means a chunk of value that could go to production. Ideally, that chunk would go to production during the sprint,…

Yes, that answers the question. Thanks, @Matt Tse 

Gotcha. If you want something more configurable than out-of-the-box JIRA Cloud, you may need to investigate the marketplace for potential add-on features, or build an app using data from the REST API. Best regards, Bill

Hi @Rachel Robins Thank you for this information! I wondered about something you note at the beginning of the post: We've previously considered making the project public, but have to balance the risk of people inadvertently sharing sensitive information when seeking help and describing their problem (it's more common than…

Hi @atsalolikhin -- Welcome to the Atlassian Community! How are you sending these reports? For example, email, Slack post, etc. Have you investigated the automation rule features? You could build a report using your JQL, and trigger or schedule it to send the results with a bit more formatting than with a subscribed…

Hi @Omar Ali I encourage you to first consider what you want to make visible. Do you want project by project information, a roll-up of some aspect, etc. After you know that, you can investigate the dashboard gadgets and create JQL queries to support them. Please review this documentation for the gadgets which are available…

Hi @Lori I am confused by what you are asking. What problem are you trying to solve? The things you describe, Business Peer Review and Architecture Review, seem more like steps in your work process rather than sprints. Would you please clarify a bit so the community can offer ideas? Thanks! Best regards, Bill

Hi @Sam Medlock- Matthews A board is a view of one or more projects, displaying the issues returned by the filter. As you describe it, I believe you have multiple projects using Scrum boards, and then you roll-up the results to one company-level board. Is that correct? If so, the company-level board (with multiple…

Removing duplicate reply due to some site/posting latency issue.

Hi @Matt Tse Thanks for the information, and that wasn't what I meant, so I'll try explaining another way. As a product person, you know backlogs go stale over time...and there are several ways to manage that, such as best-by dates, truncation, periodic refinement, "no backlog", etc. I was asking about the older items in…

Hi Kara-Lucia, Sort of... Once we learned about automation rules and had a good understanding of our workflow, it was easier. What we built can be re-used by any team in our instance. It took us a few days to figure out the automation quirks, implement, test, and deploy. Here is a summary of the steps: * Confirm the team…

Thanks, @JOY for the clarification! If your project is Next-Gen, you cannot have multiple boards or quick filters for the approach I described. In that case, you might consider moving the bugs to a different project for management by a separate team and board. (That smells like a bad idea to me, as it reduces the…

Hi @JOY Yes, that is possible... I wonder why do you not want defects (bugs) listed in the backlog? Are defects resolved outside of JIRA management? Next thing, are you using a Classic project or Next-Gen? If Classic, one solution approach would be: * Have a board that only shows stories and tasks. You can adjust your…

Hi @Kara-Lucia Are you asking a question about time in status, or just providing visibility to the suggested feature? There is already an out-of-the-box JIRA, dashboard gadget to show average number of times in status, and I find it unhelpful for what it can show. There are marketplace add-ons you can buy to show time in…

Thanks for explaining that! We do a similar thing with "abandoned" issues, where an issue moves to done and we mark a custom field for later reporting... And exclusion from board reports. For us, it is more of a disposition of done-ness, rather than a status by itself. __Bill

Hi @Dennis_H What does "lost" represent? Understanding that may help give you more ideas/options to consider. Thanks, and best regards, Bill

Hi @sofia.pedro Sorry for the long answer, as I want to try to answer all of your questions... At this time, you cannot iterate over a smart value field list, like Labels, to process the values separately in the branch. That feature is in the backlog here: https://codebarrel.atlassian.net/browse/AUT-546 Let's look at your…

Hi @Andrew Rover -- Welcome to the Atlassian Community! Have you looked at the automation rules to do this? You can catch triggers for commits and then send notifications. Please look here for starting information on the automation rules:…

Hi @Mathieu_ -- Welcome to the Atlassian Community! I wonder how you are using the estimates and Scrum board-level of JIRA reporting for the methods you have described. If the estimates are only for planning purposes, as a result of work carry-over between sprints and work items defined as UX, BE Dev, Integration, etc.,…

Thanks! As Jack noted, once they are assigned they will appear with Assigned to Me.

Yes, and to what John suggests... @Des_Kelly when you use the automation rules, you can narrow the triggering event and time frame to get the result you want. For example: * Trigger: field value changes for Component * Condition: updated in the last x minutes, perhaps using your JQL * Action: notify you by sending an email…

Hi @Mamikon Papikyan Or... rather than having two pieces of information in the Summary field (source and summary), consider using a different field to indicate the source, such as Labels, Components, or a custom field. That will make searches, analysis, and updates easier in the future. Best regards, Bill