Mykenna Cepek Expert

Hi @Vladymyr Postnov, you've got some noteworthy contributions here! I like the HAR file scanner. I might delegate a trial of it to my colleague who went down that rabbit hole, and see if it helps him learn anything new or more actionable. I'll report back (just don't hold your breath on when!) I find the atlassian-status…

This wonderful article is focused on numeric values, but I've had challenges lately with even string values in Jira Cloud automation. Crazy, right? Lately I've been making Web Requests to Jira REST API endpoints to get back the content of text fields. Dumping them with Log Action seems to show string content (e.g. markup…

My sense of the self-extinguishing comes from two areas: * My own feeling of exhaustion about the overhead of "doing my part" in reporting a bug with suitable information. I "intuit" the ROI sometimes and just let it go. The downsides include the fan-out multiplying the org cost beyond just me, and guilt that I'm one of…

* I expect our Jira Admin team (2000-user site) hears about things of this type at least 5-6 times per year, perhaps more. It may have self-extinguished somewhat over time due to the difficulties we're discussing. * It's going to be a ticket to them regardless. The ticket content will need to be as specific and detailed…

We might have seen this movie before, and the people who know the ending are those who experienced Jira automation usage caps.

The top thing that comes to my mind is troubleshooting cloud problems. Compliance-sensitive organizations have a lot of internal focus on network safety, which can manifest in various unhelpful ways (example: whitelists). Networking and security groups typically don't have abundant time to look into intermittent or…

Fantastic topic, @Trudy P Claspill Ticket-focused teams can fall into this pattern if they focus on SLA/SLE metrics at the expense of accumulating tech debt, excessive customization, or feature sprawl. Which do we want to incent: a fast fix that creates future problems, or the right fix that doesn't? Leaders can help teams…

I prefer to work backwards from the needed data to processes for gathering that data. In other words, first figure out what the true needs are for reporting, then focus on the fields in Jira which supply that data. Once there is clarity on which Jira fields are important, the team(s) supplying data in those fields need to…

I have a new perspective on this topic. I'd really like to know your thoughts on it. I would assert: heartbeats generated at the start of a Jira automation flow are better. The article above instead proposes generating them as "the last action" (step) of the flow. Why is earlier better? Firstly, it's easier. As I developed…

I have a working prototype using only native aspects of Jira and Jira Automation. Key details: * Each watched flow is paired with a work item in the same Jira Space. * A watched flow needs to only update one numeric, timestamp, or string type field in that work item. Your Jira instance should standardize on the field to be…

Thanks @Peter Kerrigan for bringing attention to this aspect of tech debt hiding in Jira workflows. A few comments: * "When someone says 'Jira changed my ticket by itself,' a post-function did it". Maybe. In our instance, we discourage transition and workflow complexity. Jira Automation is usually what "did it" in our org,…

I'm of two minds on this... * I like this @Suresh (it's occurred to me too). It's a way to get broader visibility to a curated set of bugs and suggestions in order to increase the voting on them. This makes them more likely to get Atlassian's attention. If that's the system, let's work the system towards the change we…

Thank you, Cam. Appreciate hearing back. Best wishes to you and the team.

I'm glad that this migration is complete. And I'd like to offer some feedback about the impact it had on our Enterprise-level org. It was not flawless, and I'm still fixing things. Throughout the hundreds of Jira automation flows defined in our Jira Cloud, there were some that used the prior "Send email" action. Those…

A Jira Cloud automation rule can be triggered by an incoming webhook. Assuming your organizational networking permitted the integration, that can be used to "import" arbitrary data and allow the rules to act on that data. A rule to set User Properties would need to have a Jira Admin as the Actor. You could design the rule…

I appreciate what @Greg D wrote above. And I want to temper a few parts of it with my perspective. [Advanced Forms] do work in Jira directly in some environments, but that’s usually via exceptions / special configuration these days with new sites. I was pleased to notice recently that Advanced Forms are directly available…

As noted on 13-Oct-2025: Q: Why can’t I drag-and-drop to reorder when grouping or filtering? Drag-to-rank only works when sorting by “Rank.” Grouping and certain filters override the ranking sort order, which disables drag-and-drop for now. The Drag-to-rank feature currently available in our All Work tab doesn't work by…

Thank you for the update, @Camilo Gomez. It sounds like there is no planned rollout timeframe at this point. And I'm fine with that since I have no urgency for the other email component. It's more critical that any eventual cutover to the new email component not impact the rules we already have running across our org, as…

It was driving me absolutely nutty that {{issue.summary.left(varQty.asNumeric)}} did not work! To find out that "None of the other text functions will work directly with a variable..." with or without the asNumeric conversion was so very super helpful. Do you know if there is an existing suggestion or bug toward fixing…

Scrum boards in Jira have a strong relationship with the "Story Points" field because that data drives the Velocity metrics which are built-in for Jira Scrum boards. Kanban doesn't rely on Velocity, but the "Story Points" field can still be used. It's frustrating that it doesn't radiate as clearly on the cards on the…

A best-practice is to use the ID (like 10011) rather than names (like "Story" or "User Story") for things like this (integrations, automation rules, even filters) -- as @Rik de Valk _Brainboss_ suggested (please accept his answer). We recently had some widespread impact when a Jira Admin changed the name of a highly used…

This documentation might help clarify how the Jira work item hierarchy is structured: https://www.atlassian.com/software/jira/guides/issues/overview#what-is-jira-work%20item-hierarchy

For reporting bugs and UI issues, consider either Forms or (better yet) Advanced Forms in Jira as the front-end of for that type of work intake. For user interaction tests, I am going to assume you mean "how can I team use Jira to support their visually-oriented testing?". Marketplace Apps like "Tricentis Test Management"…

For your first question, I recommend the REST API endpoint you found that differentiates "classic" (Company Managed) vs "next-gen" (Team Managed) projects spaces. I'm using that in my automation rules to differentiate the types of projects. For your other two questions, I'll just admit to owning a t-shirt that says…

Not yet. As noted in my response to another answer here, someone else here is working on this. The support ticket we have open with Atlassian is proceeding very slowly. No progress as of yet.

Tests like this help when there are no connectivity concerns, and the focus is correct credential data or correctly formatted web requests (proper endpoint, http headers, etc). They're a fine first step, but far from definitive. Such a test will come from a user's computer or laptop to the endpoint, rather than from the…

@Urmo - It's here now:

@Scott Bell - Thanks for the reply. I hear that this is MVP. I think we'd agree that the hassle factor is currently high for fully backing up automation rules with this cool new API. I think we'd also agree that the ideal Disaster Recovery plan for automation rules would be to manually import a single JSON file of all the…

It seems misleading to write "you can create hierarchies" and also write "It’s still a flat model, where all ideas are at the same level". The more accurate statement was "you can use views to visualize them in a hierarchy", but that was pretty buried and subtle. The title of this article is "Hierarchies in Jira Product…

I must be missing something. I'm excited about this API, but not finding what I was expecting. The "previous post" link above (as of today) goes to an article that talks about the orchestration (advanced) components and doesn't mention the automation API. I think it should go here instead. I understood that this API was to…