Mykenna Cepek Expert

I'll offer several suggestions, based on what the teams I'm currently working with have found useful: * Set unassigned Subtasks to same Assignee as parent - This rule is invoked manually on a Story-level issue. Commonly used after creating a bunch of new Subtasks on a Story. * Fix the Epic Name in bulk - This rule is run…

As @DPKJ requested below -- can you provide the steps to reproduce what you are seeing, so that we can be sure we're checking for the same thing?

I just checked our instance. I like to use the code formatting liberally, where it makes sense. I don't see any size problems on a couple of pages where I checked on our site. I see from the Atlassian Status Page that Confluence did have an editing related issue yesterday, which was also resolved yesterday. So if you're no…

I tried to use these today. Most of them worked (note: use all lowercase in the "Icon URL" field). However, I could not get high and medium to work. Both of these priorities show the old icons, not the new ones (png and svg). Maybe someone else can confirm this in their Jira Cloud? (Edit: originally wrote "highest" instead…

A great overview of ways to use the sprint-oriented JQL functions. Thanks @Daniel Ebers 

The bottom four appear to relate to apps which have been added to your Jira instance. You could also put in a request to the app vendors to allow an option for whether they offer access in the project sidebar -- not all do. I find this particularly annoying, especially when the app isn't used in the project. Some apps…

There are a number of known visibility problems which existing Space Permissions haven't addressed. Just a few examples: * Visibility concerns are not restricted only to viewing a page. Page titles can be revealed in the "Recently Updated" macros and the new Confluence home page "Feed" section. New page notifications are…

Again, using the Jira REST API gives you the most flexibility, as you can code things however you wish (within the confines of the API functionality). If you wanted to keep it all within Jira Automation, then the "Advanced (JSON) Editing" capabilities of some Action Components might be worth exploring. There you can use…

I mean this should be used very carefully only on specific cases when I have a custom field or property in issue level and I want to add somekind of "lock" to prevent update on the same time and give enough time each update follows through My understanding of "Refetch issue data" is that it only re-reads the data for the…

The point here to write a JQL that "scan for Stories with changed FixVersions since the rule last ran" I need to store then "previous" value in a issue property or custom field so in JQL is compare Fix Version with that value. Actually, no. Look for this in your "Branch rule/related issues" component: Enabling that will…

You definitely have a complicated use-case, with 3 rules potentially running at the same time, potentially reading and writing data from/to the same issues. This is a known problem (IMHO) with Automation, and one that is not easily solved. Note that allowing rules to trigger when an issue changes is a great feature, but a…

One workaround I can see, given the capabilities of Automation today, is to switch your ruleset from being trigger-based to being timing-based. The downside is that the fields you are maintaining (e.g. FixVersion) will not be updated ASAP, but merely "soon". For example: * Rule 1 triggers every 15 minutes to scan for…

I've struggled with a similar problem over the last 2+ years. We've got a Confluence page for our "Company directory" and leadership was clear that photos were required. Two years ago I was able to specify "width=100px", which was fantastically deterministic. But the New Editor features, and other updates since then for to…

Something not mentioned thus far is "Jira Hygiene" -- minimizing the amount of low-value and zero-value stuff in your Jira instance, most of which has accumulated over time like lint in your couch. Examples: * Unused workflows, unused anything (this is zero value, and leads to user and admin confusion). * Duplicate or…

This is where Company-Managed (classic) Projects can really help. Although if you have 20 teams already using Jira, you might already have a lot of sprawl. An early goal might be to coalesce as many workflows as possible into a few. Ditto for things like Issue Types, Statuses, Priorities, etc. Standardizing and working…

Now, if you are willing to do ONE download, then it seems that Chrome has something built-in to do exactly what you want -- for that one file type, in the future. After the download, look in the options at the bottom of the Chrome window, open the menu for the downloaded item, and note the second option: However, note that…

This is actually a browser issue, not a Jira issue. Based on what I read in this existing (and ancient) feature request for Chrome, it's not supported. But the ticket suggests that IE and Firefox (circa 2010 anyway) did support this feature. It also sounds like there used to be a Chrome extension that implemented this, but…

Update: Checking today, I see this for our instance: * "buildNumber":100166 * "buildDate":"2021-06-17T12:42:41.000-0400" Thus, the buildDate changed, but the buildNumber didn't. My conclusion: don't rely on the buildNumber.

I checked the Jira Cloud REST API, and didn't find any operations that read or update the "favorite" (star) setting for a project -- per user, or otherwise. Since it's not supported in the API, it's unlikely that a Marketplace App will support such a feature either; sorry. I believe the only way for an Admin to do this is…

Using double-quotes around non-trivial fields (or all fields) is the way to do it, as documented here. I created a simple test CSV file: Summary,Description "LMGTFY","Let Me Google That For You: https://lmgtfy.app" Importing it seemed to work fine:

That's interesting, and it's a first step towards dealing with the mess that is currently "issue relationships in the Jira issue hierarchy". However, these updates to the Jira API are only the start. Since Automation is dependent on the REST API, these updates to the API have to occur first. Then Automation has to be…

Be sure to vote for it!

The message you got is the best hint about what's likely wrong: the underlying Filter. In the Roadmap, go to the "Gear menu > Configure" and see what's shown under "Source data > Issue sources". Here you can select one or more Projects, Filters, or Boards. For whatever is shown, track down the actual Filter being used…

Keep in mind that a rule can be scoped to just certain projects, which can drastically reduce the number of monthly executions in a large organization. Remember too that you can monitor your automation usage on the main Automation admin page: If your support ticket spawns an issue on jira.atlassian.com, please feel free…

Interesting. I went back to retest, and I did confirm that the "Field Value Changed" trigger for "Parent Link" does NOT fire when "re-parenting" a Sub-task or a Story. I found existing bug JIRAAUTOSERVER-79 which hints that the "Parent Link" field relates to Jira Portfolio usage. After researching elsewhere (here and here…

I've had success clearing cookies/data for the misbehaving site. In Chrome: "Preferences > Privacy and Security > Cookies and other site data > See all cookies and site data" and then enter a portion of the domain to search for (in your case: "thd.atlassian" should be enough). You can start small (and just delete cookies)…

The official answer is: you can't. (hint: I wasn't happy with that answer either) Atlassian continuously deploys updates for Jira Cloud users, and (ignoring phased rollouts) all Cloud users are by definition on the latest version. For most users, there really is no need to know. You're always up-to-date, and what's not to…

Part of the problem is that "Parent Link", as offered in the "Field Value Changed" trigger, watches for Story/Epic links that change -- not the Story/Subtasks relationship. [UPDATE: The above is INCORRECT; the "Parent Link" is not related to the Story/Epic relationship; further details in my later comment below]. It's…

You could also consider notifying the user who attempted the change, to let them know that their attemped change was reverted. An "Email" action would do that.

The standard macros that come with Confluence Cloud don't include this capability. I explored a few other related macros, but date ranges are not offered. CONFCLOUD-14173 was created years ago to request this feature, but has since been closed (likely due to lack of votes). You could also vote for CONFSERVER-55051, which…