John Funk Community Champion

haha - I hope that works out until they get an updated version for you. :-)

I believe she is wanting two different filters on the same board. Which is not possible. The backlog view of the board and the columns on the board are really all part of the same board. Each of those sections use the same filter - you cannot have different filters for each section. 

Hi Darren, Can you give us an example of what you want use to create the issues? And why would you do that from the description field and not another more dedicated field? 

Hi Shawn - Welcome to the Atlassian Community! Batching in the link is for the Server version. You should click on the Cloud tab at the time. Or this link might take you straight there. https://confluence.atlassian.com/adminjiracloud/configuring-email-notifications-776636790.html There is no batching listed under the Cloud…

Hi Joao, Do you already have a rule started? Can you share a screenshot of it?

Hi Laura - Welcome to the Atlassian Community! Can you share the error you are getting? Where are you adding users? 

Great! Glad you got the first part working! You might be able to do the last one with some combination of validators on the create transition on the work flow. The easiest way would be to have different workflows for Sub-tasks (we do that). Then in the workflow(s) for the other issue types just add a validator that the QA…

Hi Eddie - Welcome to the Atlassian Community! Take a look at this previous post and see if it helps you solve your error: https://community.atlassian.com/t5/Jira-questions/Issue-with-login-and-redirects-when-changing-from-JIRA-to/qaq-p/72624

Great! Glad I could help. :-)

Oi Luiz, Provavelmente, você pode fazer isso de duas maneiras. * Crie uma função de postagem que envie um email quando a transição for executada. * Crie uma regra de automação para Jira que envie um email com base na transição.

Hi Alex - Welcome to the Atlassian Community! You could probably solve this a couple of ways. 1. One is to create a separate board with a filter that only shows issues where the assignee = currentUser() 2. Be sure to share that filter across your organization or with just the project role (or group). 3. Update the product…

Hi Linda - Welcome to the Atlassian Community! It's an Old Jira Issue View versus the New Jira Issue View. It works in the Old view but not yet in the new view. You can vote for and follow the support ticket for the New view here is you like: https://jira.atlassian.com/browse/JRACLOUD-69548 If you don't want to fully…

So the offset field is a number field? I missed that, sorry. I don't think you are going to be able to dynamically use the value of the field with the current smart values syntax. You need to use the code I have above, but I don't see a way to make the "5" in my example an actually field. @John McKiernan1 - Any thoughts on…

Hey @John McKiernan - Now that the ticket has been marked Done, do you have an estimated date for shipping?? :-) Not that I am anxious or anything ...

Hi @김소영 - You might need to go ahead and create a support ticket with Atlassian. I am not seeing any problems with mine - I see the names for the same gadget. https://support.atlassian.com/contact/#/

It means it was moved to Open more than 5 days ago and is still in Open. Is that what you were looking for?

Hi Pavle, You could create an Automation for Jira schedule rule that runs at certain times. What type of information would be in the email?

Hi Avner, Try this: Just to let you know that<a href="{{toUrl}}"{{issue.key}}> issue</a> is Ready to Test!

Hi Marina and welcome to the Atlassian Community! We are glad you are here!!

Hi Rick, I think you will need to use the Diff date feature to get a number first - and save that to custom field. I would do that one one (or either) of the dates is updated. Then you can use the proper code to set the date. Something like: {{triggerIssue.duedate.minusDays(5)}}

You can follow along with the Next-gen roadmap here: https://www.atlassian.com/software/jira/whats-new/next-gen?_ga=2.104316484.513035551.1586779195-1313086432.1576012938#intheworks

Hi Alexander - Welcome to the Atlassian Community! I suspect the limitations you are running into are because you are creating Next-gen projects. If you create a Classic Software project, you might find that you can do the things you want to do as listed above. 

Great - glad I was able to help a little. :-)

Your first rule above is based on the change in a value of a field (not a status). Your second rule needs to be based on the the task in Project A transitioning to a certain status. Then that causes the issue in Project B to transition to the same status. You need need a third rule for when B transitions to a status and…

Hi @Shikh Ahmad Hafidz Bin Shikh Ahmad Marzuki , Try: {{issue.customer.displayName}}

Hi @Shikh Ahmad Hafidz Bin Shikh Ahmad Marzuki , This is what I use: {{issue.customField_17038.convertToTimeZone("America/Chicago").longDateTime}}

¡Hola @Mariperla Macias y bienvenidos a la Comunidad Atlassian! ¡¡Nos alegramos de que usted está aquí!! Saludos

Hi Amanda - Welcome to the Atlassian Community! You probably need another board to show the other issue types. There's not really a concept of a sub-board - it's just another board. Most tools that measure WIP, Time In Status, Lead Time, etc. are going to use the board. So if certain issue types shouldn't be measured, then…

Great! Glad I could help. :-)

It's not a nice clean way, but this works: https://community.atlassian.com/t5/Jira-Software-questions/Migrating-from-Classic-to-Next-gen-Software-Projects/qaq-p/918856