Kelly Arrey Expert

I can't like @Ben Ernest-Jones' comment enough. 

Well done @Mohana Sundar J ! Thanks!

This is a positive step (back), but I think it points out a larger problem, which is that Atlassian seems to be focused exclusively on optimizing to attract new customers, without consideration of the effects on the installed base. The obsession with renaming things for marginal benefits, while ignoring functional and…

Hi @Mark Schweighardt, As far as I can see (on cloud), we don't have the option to move Tasks one level below Stories in the Jira native Work Type Hierarchy. Our approach, which we developed before there was a Parent field, is to use issue links to extend the built-in hierarchy. We've defined a custom issue link type we…

@Bobby Reeves @Stefan Salzl Just came across this: Enhanced Querying with JQL

Thanks @Akhand Pratap Singh this is a great article! Can you do one for Confluence too? Too many new Confluence users run screaming from the room when their inboxes get buried in notifications.

@Hugo Navia See also @Deidre East's comment above! 

"These guides do not only get outdated really fast- we have no awareness of when they do!" @Marta Zapatero Congrats! You've just identified a hole in Atlassian's development process and Definition of Done!

Hi @Carol Low, I wish I could like @Deidre East's comment a thousand times. Merging "duplicate" fields is one of the headaches inherent in consolidating multiple Jira systems into a single system after an acquisition. Any help you can offer in this situation would be most ... helpful! Thanks, Kel

@Shalu Pandey @Simon Kliewer 3 years on, we can embed a SharePoint Excel successfully, but, as noted and liked by multiple community members three years ago: * You still can't get it to reliably display a specific tab in the Excel file * You still can't tell it how much of the specific Excel tab you want to display (e.g.,…

In the beginning, there was Jira. Then there was Jira Software and Jira Core. Then there was Jira Software and Jira Work Management. And now there's Jira again. And just today I got this popup: And I also remember seeing somewhere that Jira Projects will soon be called "Spaces".

Hi @Wendy Grapentine, The non-automation approach to solving this problem is to "watch" the page as described in the Watch pages ... documentation. HTH, Kel

@Tanguy Crusson @Bueller? @Bueller?

Hi @Carol Low Thanks, we're really looking forward to these changes. To follow on to @Bill Sheboy's point above, I'm also very interested in how this is going to affect JPD/Team-managed project fields. The challenge that I have now is seeing stuff like this when I'm trying to write a filter or adjust filter columns: There…

Hi @Danno, my apologies, I thought we could add a condition to the Create transition but the Create transition apparently doesn't support that.

If you want to enforce "Conditions" or "Validators" on a workflow transition, use Workflow "Conditions" and "Validators", not "Properties". See Configure Advanced Issue Workflows.

Thanks @Bill Sheboy ! Bookmarked this one!

Hi @Marc -Devoteam-, yup I get what you're trying to do. Sorry I don't have any more ideas. 

Hi @Marc -Devoteam-, I found this - thought you might want to vote for the Suggestion: Just me thinking out loud, but can you come at this from another angle? Parse the linked ticket number from the Confluence page and than pass it to Jira? This page seems to suggest that you could transition the Jira ticket in a…

Hi @Shiva Kumar Hiremath, Please share screenshots of the details of your rule as it exists right now. Thanks, Kel

Yup, I also bailed when the questions got intrusive and irrelevant to my experience as a Jira Admin.

@Shane Kelly Yup. Also, optimizing for people who haven't even bought the product in an effort to remove perceived barriers to entry, at the expense of incurring needless frustration and wasted time for literally millions of users who already pay for the product.

Hi Ajaz, JWM is being absorbed back into Jira Software and the result is called "Jira". Atlassian is migrating JWM licenses to Jira over time, so, as John said, this won't be a problem going forward. Here are a couple of articles for context: * Jira Work Management is now part of Jira * Just Jira - JWM's Merger back into…

Hi @Alexandra Martins, I think there are two questions here: * Can you do this? * Should you do this? Marking everything as Done unconditionally, automatically, without any investigation, seems like a risk that outstanding work will be mistakenly marked as completed, which can lead to problems down the road. Best regards,…

Hi @Bachir AMMACHE, Can you share screen shots of the relevant details of your current rule? Thanks,

Hi @Josh Sherwood, Thanks for the update. I think it's safe to say that the community is quite perplexed about this initiative. The community has offered a lot of feedback on the issue, and it's not apparent that any of it has been heard. A company which includes statements like "Open company, no bullshit", and "Don’t #@!%…

Atlassian snatching defeat from the jaws of victory, yet again. They're tickets. :eyeroll: Jira tickets don't necessarily represent work: They can represent people, assets, etc. "Ticket" can be applied to any of these with no loss of clarity. "Work", not so much. Who says "Go open a work for that" ? I would draw your…

This seems like a no-brainer. Ticket makes the most sense. If you call it a "Work Item", everyone's going to call them tickets anyway. The Jira ecosystem has spent many years training users that a task is an issue type. You want to turn around and try to explain how a story is now a task type? If you said instead that a…

I was trying to help you get around your quote issue above. Sorry.

We solved this problem about a decade ago with two native Jira constructs: * Jira Groups * A Select List (single choice) field we called "Agile Team" We create a Jira Group for each Agile Team value. Then we use the workflow condition "User is in Group Custom Field". It's amazing if 10 years on, Atlassian's latest…