Mykenna Cepek Expert

I'm not aware of any native way in JQL to look up a user tag in an issue text field (e.g. Comment, Description, etc). You could look for an "@" in text, but it looks like you want to know the specific user. There might be add-ons which provides extra JQL functionality that can do this. Maybe look at Atlassian Marketplace…

I'm not quite clear what you see as the problem. Some actions will result in "Automation for Jira" being seen as the user. Do you have other automation rules which might be creating the branch that is triggering this rule? If so, then the "Automation for Jira" user is the "User who triggered the event", and would end up as…

This seems like a really straightforward use-case for a Manually Triggered rule in Jira Automation. Something along these lines:

I appreciate this periodic and highly abbreviated overview of newly available add-ons.

Good catch, @Brian Blanas - here's his fix as a visual:

The original post said "Jira administrators can also change those short project keys". And it also said: "...TEST-1234 might one day become QA-1234 [...] The issue number part won't change". Theoretically: yes. In reality: beware. Two years ago I had a project key of ABC which was in-use, but we decided we wanted to use it…

Removing "Done" items from a plan might work for some situations. But when a lot of effort has been put into defining issue dependencies, it doesn't work. We don't want to lose those dependencies, we just want the plan to auto-schedule as expected when "Done" issues are encountered. Some problems we have seen: * Done…

I get VERY concerned when I read things like "this issue navigator [will] replace advanced search in the future". I did follow the link to JRACLOUD-74155 and it did not reduce my concerns. As a power user, I almost always bypass the "basic search" and go straight to the Advanced Search. I literally cannot use basic search…

I'd highly recommend Draw.io. I recently compared Draw.io and Lucidchart: * Comparable functionality * Identical icon sets * Comparable template sets (despite what the Lucidchart PR says about Draw.io) * Import functionality that was over 95% accurate in my testing * Draw.io feels more "native" in Jira and Confluence *…

A frustration I had with the Team field in Advanced Roadmaps is that it currently is not fully supported in Jira. For example, it's not accessible in Automation. I tried to create an automation rule to set the Assignee based on the Team. Fail.

Having worked with a dozen different organizations, scores of teams, and across various industries, I'd suggest that there really isn't a single good answer for how to use Jira Projects with/across teams, products, components, etc. At a healthcare company, I worked with 3 teams all updating the same codebase for a single…

All the examples shown are in a project board or issue search results. Hopefully the Advanced Roadmaps can feel some of this love soon? Not being able to change a status value while editing a Plan is equally painful. Appreciate the attention to things that will help us maintain an up-to-date project with less effort!

My $0.02... As with gamification, the critical aspect of such a system will be the core metric which triggers a micropayment. "When a measurement becomes a target, it ceases to be a good measure." -- Goodhart's Law Perhaps some best practices will be developed to support a workable model for this. I love the concept, but…

I'm not aware of anything. It does seem like an "easy request" to "just move" issues around. But the devil is definitely in these details. Jira does simplify the steps when it realizes there are one-to-one mappings. But the "Move" process is defined to allow for the complicated situations, collapsing to rote click-thru for…

There is some merit to their request. It might be worth experimenting with workflow exceptions for a strong Kanban team that is serious about using good Kanban metrics. Some of the built-in reports for Jira can help support a metric-oriented Kanban team: * Cumulative Flow - easily visualizes states that impede flow. *…

Not one user has been confused about the default Status. If you think about it, even without a "Backlog" status for the Scrum projects, new issues still end up in the Backlog (just with Status = To Do). There was another question earlier about the actual workflow transitions themselves. We allow all states to transition to…

All of our technical teams use just one of four standard Company-Managed workflows: * To Do - In Progress - Done * To Do - In Progress - In Review - Done * Backlog - To Do - In Progress - Done * Backlog - To Do - In Progress - In Review - Done The first two are used for Scrum teams/boards, since the Backlog in Jira is…

If you want to suggest this as a new feature for Confluence, that is done here (select "Product Suggestions"). I'm not aware of a native way that Confluence would support this. I did find one relatively inexpensive app in the Marketplace that might provide the additional features you want. It might be worth a free trial…

Well, Jira Cloud (my assumption of your hosting type) doesn't allow for that fine-grained customization of UI and permissions. However, here's a creative solution to consider. Use Jira Automation to copy the links into a text field which is visible to your client users. The rule could run perhaps hourly during business…

If I can clarify... your client users have all the access they need right now in Jira, except that you'd like them to also be able to see that there are linked issues. In other words, you want client users to be able to see the links (to any "internal tickets") but not see the "internal tickets" themselves. Is that…

Being able to configure App visibility by JQL seems interesting. But at the very least, Atlassian should consider the ability enable/disable installed add-ons on a per-project level. I've noticed that larger organizations struggle more with this, as they tend to have accumulated more add-ons over time. It gets to be a LOT…

Sorry, but Jira Cloud doesn't offer this fine-grained level of control. However, what I would do in this case is set up notification to watch for when this happens. It's probably rare, but important to catch. An advantage of "seeing it when it happens" is that you'll have a great "user education" opportunity with the…

Ok, that's really weird. I'd first check that Story Points are as expected in your FEVO project. Namely: 1) Confirm that the issues shown actually have a value for the "Story Points" field. Do an issue search like: project = "FEVO" and "Story Points[Number]" is not empty 2) Confirm that the FEVO project field and screen…

Sorry, Rajeev, but the location of any added "extra fields" in the "Card layout" is fixed. Each takes up one "row", whether that's in the Backlog or Kanban/Sprint view. Maybe there are add-ons in the Atlassian Marketplace that might offer more customizability of cards. I did a quick scan, but nothing popped out at me. You…

Jira Cloud might not provide the exact low-level access control that you are wishing for here. The various types of Admin roles in Jira are fixed, and documented pretty well here: https://support.atlassian.com/user-management/docs/give-users-admin-permissions/ Check out also the "Project Admin" role, which might be closest…

Are these teams are using Next-Gen (Team Managed) projects, or Classic (Company Managed) projects? Also, are you using Roadmaps?

Thanks for this, Esther!

I just retested the directions I posted on Jan 11, 2021 above. They work fine on Jira Cloud, on my MacBook Pro running Big Sur in the latest Chrome, Safari, or Brave browsers.

Glad to hear the problem is solved. And thank you for sharing the solution that worked back to the community here!

For those following this topic, and wanting to vote for this capability: https://jira.atlassian.com/browse/JIRAAUTOSERVER-159 I also found this closed ticket that found some (inconsistent) access to the Team field via "Fields Changed" in Automation. But there is no joy here:…