Mykenna Cepek Expert

Hi Chester, I have two thoughts here... Firstly, based on your second post here, specifically the simplified "rule in other words", you can simplify your rule as follows: * Trigger: "Issue Created" (this is probably fine as-is) * Condition: "Issue Fields" (check user is in organization) * Condition: "Issue Fields" (check…

Not that I know of. It's been asked for a number of times. Your vote on CONFCLOUD-70244 will help encourage Atlassian to fix this. Thanks.

Please also consider voting for this to be fixed: CONFCLOUD-70244 And perhaps add a comment there also pointing out your use-case (that, as a user rather than an admin, you want to clean up your own drafts). Thanks!

Please also vote for this to be fixed: CONFCLOUD-70244

I believe a Team-Managed (NextGen) Project can be archived (sort of) as follows: * Go into "Project Settings > Access"* Ensure that the appropriate admins are listed for the "Administrator" role. * Remove all other users from all other roles. The net result is that only admins will have visibility to the project. It…

The existing ticket on this topic has been closed: JSWCLOUD-17494 However, it looks to me that a Team-Managed (NextGen) Project can be archived (sort of) as follows: * Go into "Project Settings > Access" and change:* Ensure that the appropriate Jira admins are listed for the "Administrator" role. * Remove all other users…

Several things you can check: * The plan might be relying on a Filter which excludes subtasks. Check that under "Settings > Data Source" for the plan. * Subtasks may have been excluded from the Source Data for the plan. That's under "Settings > Exclusion Rules". * If the above looks ok, confirm that the "Hierarchy" setting…

I think the reason Jira import works this way is because when exporting issues, there is no guarantee that the parent story will appear earlier in the export than it's child subtasks (for example). Similar problem with Epics and Stories. There are two approachs that will work, between importing "everything" and importing…

My assumption was that most users can edit the ticket (and the specific field in question), whereas there is a group of users who should not be able to edit that one field. Perhaps @Steven Rhodes can validate this assumption? Standard Jira Cloud permission schemes do not have field-level granularity.

Seems pretty straightforward, but I admit that Jira Automation can be a bit confusing. Which specific part of this are you stuck on?

I was able to validate your use case: * Log time to an issue and include a unique sequence of digits (e.g. 2468013579) in the Worklog Entry Comment. * Wait a bit (for reindexing to complete) and use Global Search in Jira for that unique sequence of digits. * Search returns an error, or no results. Digging into the docs, I…

Recent changes to Confluence have changed how image sizing works in the New Editor. I encourage you to vote for these existing tickets: * CONFCLOUD-65585 * CONFCLOUD-65597

This probably shouldn't be popping up on my (or anyone's) feed.

When using "Auto-schedule" on a plan, it gives you a dialog to select when to override existing values: Have you tried ensuring that the "Releases" setting uses "Empty values only"? My understanding is that this should prevent your milestones (aka versions aka releases) from having their dates updated when a plan is…

In terms of the "left side color bar" for cards (the built-in way that Jira can color cards on a board), that is exclusively controlled by the "Board Settings > Card Colors" configuration for a board. There aren't any "issue fields" that control card color. If you are using a Marketplace app that allows for some control of…

It would help if you could clarify a few things: * What Jira Cloud Plan are you using (Free, Standard, Premium, or Enterprise)? * Is this with a Team-Managed (NextGen) Project, or a Company-Managed (Classic) Project? * What are you using for your "final milestone"? A release? An Issue? What date(s) have you set on that…

It's always good to check the Atlassian Status Page when odd things like this happen, just in case there is a known incident in progress (in which case "try it later" is suggested). I looked back to early May 2021 for Jira and didn't see anything related. For others experiencing something like this, one suggestion is to…

Hi Gale. Sorry, but there's too little information here for us to help. Some questions: * What are your "Test types"? * Which App are you using that provides the linksHierarchyIssue() function?

Jira Cloud doesn't have JQL subqueries or the kind of aggregate "issue link" functionality you are needing here. So out-of-the-box you will not be able to construct the JQL you need for this. There are likely to be apps in the Atlassian Marketplace that extend Jira's JQL capabilities. You'll likely need a paid app, but…

Have you tried this: * Board Settings > Estimation * Change the "Estimation Statistic" to "Issue Count" or "Story Points"

Can you clarify why it is important to have imported Jira issues created in a specific order? Are you trying to control what Jira Key is assigned to each issue? Or is there some other goal?

A few options to ponder: * Simply closing the issues will allow them to "age out of view", depending on your board settings -- if waiting a week or three is ok. The advantages here are: minimally changing the existing issues, and everything stays in that project. * If Scrum is being used for this project, you could create…

Is this team using a Team-Managed (Next-Gen) or Company-Managed (Classic) project?

Have you checked the Backlog? Cards typically start out there (unless the Status is changed when the card is created). Otherwise, try this: bring up the original card in one window, and the cloned card in another window. Because you used Clone, they should be fairly similar. Then compare each field between the two cards.…

We use Tempo Timesheets, and it handles roll-up great -- not only to Epics, but to orthogonal elements that they also support (Accounts and Customers). Beware: some solutions assume that all time logged to an issue relate to the Assignee of an issue. There can be team use cases where reassigning an issue might be part of a…

The add-on mentioned above is currently worthless for managing user entity data.

I'm a little confused by your explanation, since a Post Function should only run when an issue transitions into that particular state. Editing a custom field on an issue (using automation or otherwise) shouldn't trigger a workflow post function. I'm probably just not understanding a detail of your implementation. - - - - -…

Wow, you're right. As far as I can find, the "note" you see when configuring the "Update issue custom field" post function seems to be the entirety of the documentation for those "macros". While it makes sense to try to use a post function for this, have you considered using Jira Automation instead? It's fairly easy to use…

It might help to know that the markdown formatting in the Description and Comment fields in Jira is not a pure "rich text" equivalent. You might be used to being able to copy and paste text from Word Processing and Spreadsheet applications (e.g. Word, Excel, etc) freely and have their text attributes maintained. But…

My one thought is to label all the "inbound pages" (the pages being used for the inbound links). Then you can use the "Content By Label" macro to aggregate a list of the outbound links on that "A" page. - - - - - - - If that's feasible for you, great! Just one additional caution. You might already have a template page that…