Bill Sheboy Expert

Hi @John Funk For a scheduled trigger, I think that would end up sending an email for each issue found. One challenge is the custom date fields aren't available with LookupIssues, so that cannot collapse to one email. That is why I was thinking of the custom field to store the date difference and treat reporting/analysis…

Hi @Ben Jasinski -- Welcome to the Atlassian Community! Short answer is: no, you cannot do that with out-of-the-box Jira, and... This type of analysis can be tricky and controversial. Story points, to many teams, are often considered an indicator of complexity and/or relative effort and/or lots of things. Trying to…

Hi @Shawn Bates Do you know the version ID? If so, you could just do a JQL search on fixVersion=myID with https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/search If you know more about the version, you could use the JQL functions in the query, such as project = myProject AND fixVersion =…

Hi @Dennis_H Yes, and to what Jack noted... How often do you need to perform this query/check? * one time: export to a spreadsheet and check with a formula * lots of times: consider purchasing a JQL add-on from the marketplace * somewhere between one and lots: add a custom field for the days difference between the dates,…

Hi @Taylor Boswell You may also want to try asking this question in the developer community: https://community.developer.atlassian.com/ Best regards, Bill

Neil, if this works for you, please consider marking this question as answered. That will help others with similar questions find solutions faster. Thanks!

Hi @Titus.c I do not believe that is possible with automation yet. Here is a suggestion to add the feature: https://codebarrel.atlassian.net/browse/AUT-1648 Looking over the advanced edit with JSON functions, you could structure an update with a remove, although I am unclear if that would work. It seems the only way to do…

Hi @Becky -- Welcome to the Atlassian Community! Is your question about Trello? If so, you may want to post it on that board to get ideas: https://community.atlassian.com/t5/Trello/ct-p/trello And you may want to look at this post for ideas:…

Hi @Steven Codd -- Welcome to the Atlassian Community! Here is the suggestion to add field configuration for Team-Managed (next-gen) projects, backlog and board. You may watch or vote for the suggestion. https://jira.atlassian.com/browse/JSWCLOUD-17336 Best regards, Bill

Hi @Michele Franklin -- Welcome to the Atlassian Community! Yes, you need an email address for an account. I have seen some community posts where people use a dummy/fake email address in this situation, but I would advise against that. Without guessing how those email addresses will be used for log-in in the future, it…

.reply removed.

Thanks for explaining, Richard. Unfortunately, out-of-the-box Jira does not handle many possible nested queries for parent/child checks. Customers often buy a marketplace add-on for JQL to enhance those features. For checks on status and the date fields you note, you certainly can test for those with JQL queries. And, you…

Hi @[deleted] -- Welcome to the Atlassian Community! Here is the suggestion (bug?) to fix that behavior: https://jira.atlassian.com/browse/JRACLOUD-76412 Best regards, Bill

Hi @Andres E.Diaz -- Welcome to the Atlassian Community! You could create a filter for a Kanban board to show the open, current sprint work: project = myProject AND sprint IN openSprints() AND sprint NOT IN futureSprints() ORDER BY Rank However, what problem are you solving by doing this? Doesn't the scrum team already…

Hi @Eric Roetenberg For automatic filter export, the built-in features only support emails using a subscription. As one alternative if you had a scheduled job, you could call the REST API for a filter search and save the results. There may also be marketplace add-ons for purchase which could add this feature to Jira. Best…

Looks like you are okay regarding any fields; the "Story point estimate" field is the one used by Team-managed (next-gen) projects to handle story points. So no problem there. Yes, I understood the symptom you observed is different from that defect. What I wondered was if the fix being rolled out was causing side-effects.…

Hi @roland.amann Smart value names are case-sensitive, so this one could be: {{issue.Start Date}} When you want to learn the name of a specific smart value, you can try this method to compare the values in an issue which uses the fields:…

Hi @Alan McCay -- Welcome to the Atlassian Community! For reporting with out-of-the-box Jira features you may use saved filter searches, under the top-navigation bar: Filters > Advanced Issue Search For example, you note an example of seeing the time tracking for a specific label for last week. You could do this with the…

Hi @Owen Scott -- Welcome to the Atlassian Community! Unfortunately, my suggestion to add the other fields to Lookup Issues got moved to the dreaded "future consideration" status: https://jira.atlassian.com/browse/JRACLOUD-75018 You may still vote for it/watch it if you wish. Best regards, Bill

Thanks for that information, Emmanuel. I tried that query and it works correctly for me. Next, please check with your site admin to learn if there is a custom field that was created with the same name as "story points". You can also check this yourself by typing in a query, starting to type "story points" and see if there…

I am glad to hear you got it to work by altering your response data. Of note, here are a suggestion and a defect related to improving the issues you note for created variables. Resolving either one of these would have made your use case much easier to implement. https://jira.atlassian.com/browse/JRACLOUD-75019…

Hi @Avnish Narula You cannot see that easily on the board. You could use a filter search and count from the end, given that is close to your target. Please substitute in your project name and status values. project = myProject AND status = Done ORDER BY resolved ASC Please navigate from the top-bar to Filters > Advanced…

Hi @Surizaday Morones Are you on the Server or Cloud version of Jira? The LookupIssues action is only available for Cloud. For Server, I believe they have {{issues}} (note the plural value) available for webhook and scheduled triggers. Best regards, Bill

Liz, that is where I have been looking for progress since 19 April. I suggest directly contacting support to learn if what you are experiencing is related or something new: https://support.atlassian.com/contact/#/ As site admin of a paid instance, you should be able to create the ticket.

Hi @[deleted] We are encountering the same issues, and it appears the incident is still active: https://jira-software.status.atlassian.com/ Best regards, Bill

Hi @Ila Sharma -- Welcome to the Atlassian Community! I have not used that add-on before, and I suggest looking at their documentation to see how they recommend finding bugs with linked test cases. It seems they have their own query mechanism separate from JQL.…

Hi @Julia Foden I was able to do this with ROUND() so you could try: {{#=}}ROUND({{now.diff(issue.created).minutes.abs}} / 60, 2){{/}} Best regards, Bill

Have you tried .asNumber That works for Cloud, although I do not see it listed in the Server documentation.

Thanks for confirming that, Lily. Although there are definitely open defects for JQL, for a complex query like this it can help to rule out issues by incrementally building/testing to see when the results go to zero. That may reveal if there is a defect or just a query error/misunderstanding. Before doing that, it seems…

Hi @emmanuel_dolley Are you using a Team-Managed project (formerly called next-gen) or a Company-Managed project (formerly called classic)? You may see this if you expand the left panel and look at the bottom. For queries, Team-Managed projects use Story Point Estimate, while Company-Managed use Story Points. Both appear…