Laurie Sciutti Expert

Hi @Jack Davis ~ if you use ScriptRunner, this should work: issuetype = Epic and issueFunction not in hasLinkType("Epic-Story Link")

Hi @Ray Letoa ~ then use the created >= -1h in your JQL and ensure the "Only include" checkbox is checked. If that still doesn't work for you then you can probably create a dummy datetime field that you set through an automation rule to equal create date + one hour that you can then use as a trigger in another automation…

H @ANISH TANEJA ~ this works for me:

Hi @Ray Letoa ~ that additional information helps! 😀 Use the Scheduled trigger combined with a JQL that searches for issues updated <= -1h. There is also an option to allow other rule actions to trigger your rule (as shown in the second screenshot below). HTH

Hi @Ray Letoa ~ can you just disable the rule and enable it with a CRON to run it according to your time period? Then disable it again. Enabling it when you need it, combined with your "countdown" time period in your scheduled trigger should do what you need...

You might also try using the "lookupIssues" smart value... https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues 

Hi @Lara Sousa ~ this might help: How to sum up story points from sub-tasks to parent issue using Jira automation - YouTube 

@Tom Garland issues show multiple sprints when they are rolled over from one sprint to another. In other words, when you close a sprint and have open issues you are prompted to either move those open issues to the backlog or to the next sprint. However, if an issue was in multiple sprints you should still see it in the…

So you inserted this link on your second page: firstpageurl#anchorname? Does anything happen when you click the link? Are there spaces in your anchor name? If so, you'll need to replace the spaces with "-" in your anchor link reference... If that doesn't work, maybe provide screen shots?

Subtasks aren't included in burndowns (only Story-level issues). Is your "Done" column the column farthest on the right on your board?

Hi @Tom Garland ~ were those issues estimated (i.e. do they have Story Points)?

VERY cool! I've thought about taking that train trip! You might have just motivated me to actually do it! 🥰

Hi @Omer Meshar ~ it depends where your page is located. If it's in the same space, you would need to preface your anchor link in Second page with the page name (i.e. First page#anchor). If it's in a different space, you would need to preface your anchor link in second page with the space key and a colon (i.e. SPACE:First…

@Dana A ~ I love this post. Thank you for sharing! If you don't mind me asking, where were those pictures taken?

Hi @Anja Eigner ~ I'm not sure you can do that natively, but you could create a quick filter (Status != "Backlog") on your board so that when selected, those items are filtered out. Curious if anyone else has suggestions...

H @Angelique Kim ~ there's some great information here, that we follow in our organization: https://scaledagileframework.com/spikes/ 

@Julie d_Antin _Elements_ ~ great question! I'm actually looking for recommendations at the moment. I prefer thrillers / mysteries... 

You're very welcome, @Éric Dumesnil !

Yes ~ but you shouldn't need the smart value since your rule is triggered on an issue transition: the rule interprets the fix version for each issue that is run in the rule...

@Éric Dumesnil ~ yep - that's a JQL statement. Just add another condition like shown below...

Hi @Éric Dumesnil ~ this should do the trick! fixVersion in releasedVersions()

Hi @Priyanka sawant ~ have a look at these previous questions / answers. I've done both and they work well. https://community.atlassian.com/t5/Jira-questions/How-to-import-stories-linked-to-epics-in-jira/qaq-p/373117…

Hi @Phil Bustin ~ you'll want to add it via the "More options" section...sample shown below.

Hi @Mark Kinley ~ I don't believe the Flag color can be changed. You can, however, add a custom color to your Card in your Scrum or Kanban view via the Board Config. Simply add the following (in addition to whatever you are using to indicate Out of Office users):

Hi @Selvalakshmi Suyambulingam ~ welcome! This should work: issuetype = Defect and created >= startOfDay()

@Georgina Vint ~ are you creating a linked QA issue? If so, you would want to use the Related Issues condition instead of just the JQL condition. If that still doesn't work, can you provide more details of your existing automation rule?

@Georgina Vint remove the "In" portion...

Hi @Georgina Vint ~ you should be able to use something like status was not "QA", provided there is no other transition to QA other than from "In Progress"...

Hi @Preem Prakassh Dayaal ~ here's a similar rule: https://www.atlassian.com/software/jira/automation-template-library#/rule/9918920. You would need to replace the "Send email" action, with a "Comment on issue" action...