Jane Yeoh Atlassian Team

@Hannes Obweger - JXL for Jira , Yes, we've been made aware with a few reports around the doubling up of the category field. We're in the process of rolling out a fix (may take up to a week or two to reach everyone) that will handle a couple of the scenarios that this bug seems to manifest itself in. 

Hi @Amelia Giuliani , Glad to hear that this has been resolved. We did take a note of this bug as this was reported earlier by a few customers, we're in the process of rolling out a fix but please feel free to reach out if you have any more questions.

So @Walter Buggenhout is right, it is a Comments column so you're able to access comments quickly for individual items.

Hi @Spencer Applegate , Thanks for your question! I'm Jane, one of the Product Managers from the JWM team. We're currently recruiting research participants who can help us understand the need to have a space where they're able to see a consolidated view of their projects. If you're interested, I would love to invite you…

Yes that's right! This feature isn't currently available. 

Hi @Sara Palmitessa , Can you please send me an email to jyeoh@atlassian.com with your site name so we can have our team look into this for you?

Hi @Becca Colbaugh We've just rolled this out to 100% so you should see this available on your list view in your business project.

Hi @Andy Beard ! Thanks for your feedback. We're still in the early stages of improving a lot of functionality in Jira Work Management, and will be continuing to release features for the board view over the coming financial year. Of the ones you've mentioned, how would you rank these in terms of importance? What kind of…

Hi @Victoria Inman , Thanks for reaching out. It looks like the view you are seeing now is the nested view (Epics > Tasks > Subtasks) which we recently shipped while in your previous view, you were seeing Epics and their tasks un-nested. We are working on a quick expand all/collapse all capability so you can choose if your…

Hi @Marcelo Neves , I apologise for the delay in my response! This should be shipped to all customers now. Are you able to please see if you can now see this option on your board? If not, please reach out to me directly via my email: jyeoh@atlassian.com. Kind regards, Jane

This is fully rolled out so you should all be able to re-order your columns in the list view! 

Hi @Dennis_H @John Funk , Sorry, I'm only now seeing this! Dennish, I'm Jane, one of the Product Managers on the Jira Work Management team. There has been some recent updates to the business boards that we have been rolling out and contain some of the changes you've mentioned here. I would love to book in a quick feedback…

Hi @John Funk and @Andre Menezes , We're actually in the process of rolling this out, so you should hopefully see this supported soon! 

Perfect! Glad to hear! @Curt Holley @John Funk 

Hi @Curt Holley , This is also a new known bug that we are tracking here: https://jira.atlassian.com/browse/JWMCLOUD-46 although my team has let me know that the fix has just gone out and being rolled out as I'm typing this. Hopefully this will be resolved for you shortly! 

Thanks for tagging me @John Funk , yes this was a known bug, but should be fixed now! Feel free to let me know if you find this is still happening.

Hi Stuart, Welcome to the Atlassian Community! Just trying to understand the need to create separate projects for each task. Might I suggest a different way of thinking of this. You could use the Epic-Task-Subtask relationship instead of creating individual projects for each task. This way, you would be able to track…

Hi @John Funk As always, it was a pleasure chatting and learning from you. 

Hi there, Thanks for reaching out! You're close with your rule. In your Branch rule component, instead of using 'Current issue' which will refer to the issue in the trigger, select 'Most recently created issue' instead which will then act on your newly created issue. Your rule then will look something like: Feel free to…

Hi Teza, Jane from Automation here. Firstly, thanks for reaching out. This is one of our more popular use cases and is as simple as a two step rule. It will look something like this: Essentially what this rule is doing is searching once a day for tickets that have been Resolved and not updated in the last 14 days, and…

Thanks for that Evanthia! It looks like we will need further investigations into this. Are you able to raise a support issue at support.atlassian.com with: * Details of the audit log - with More details expanded. This will tell us if your rule ran with errors, or if certain conditions have failed, or if it just doesn't…

Hi Evanthia, Jane from the automation team here. Are you able to please send a screenshot across of your rule so I can have a better look for you? It sounds like you're doing the right things, but without the configuration of your rule, it's hard to tell if there is a misstep somewhere. Cheers, Jane

Oi Andressa, Obrigado por entrar em contato. Espero que esta tradução funcione! Sim, você poderá fazer isso com automação. Eu criei uma regra para mostrar como isso pode ser: Avise-me se precisar de mais ajuda. Saudações, Jane

Hi Conor, Thanks so much for reaching out! To answer your question in the title around using strings and smart values in our Create variable action, yes you can! If you're wanting to if pull the 1.0.0 out of the branch name though, there is just a minor tweak in the smart value that you are using:…

Hi Rod, Thanks for reaching out. Yes, this is possible - your rule (very simply) would look something like this: Using the Advanced compare condition, you could check to see if the initiator's email address contains a certain email domain, and automatically deletes the issue. Hope that helps. Feel free to reach out again…

Hi Henrik, Thanks for reaching out! You can definitely do this in Automation and you will need 2 separate rules for this. First rule will look like this: Using the Scheduled trigger that checks once a day if there are issues more than 3 days old and then adds a reminder comment Your second rule is similar: Using the…

Hi Xavier, Thanks for reaching out. Yes, this is definitely configurable within Jira Automation and your rule would look something like this: Trigger: You can choose your trigger out of 34 different triggers that will kick start your rule Condition: Here I have used our Issue fields condition to check if components…

You're welcome, Adam! Sorry there wasn't a solution for you. Feel free to reach out if you need anything else. Cheers, Jane

Hi Adam, Unfortunately this isn't currently possible. Slack requires that users are mentioned via API calls, using their Slack member ID: https://support.atlassian.com/jira-software-cloud/docs/use-automation-with-slack/ That member ID is not available in Jira (as in it's not stored in Jira issues or users), so we can't…

Hi Jorge, Glad to help! Feel free to reach out if you need further help. Kind regards, Jane