John Funk Community Champion

Hi Ellen, Are all of the tasks linked to the Epics in the same project as the Epic? It might be that the filter attached to the board is ignoring some cards based on what Project that are in. 

Why do you have issue.inicident.Incident Cost and not just {{issue.Incident Cost? I think you have an extra incident word in there. 

Вы можете сравнить версию Pro с версией Lite здесь: https://confluence.atlassian.com/automation/getting-the-right-version-993924597.html

Can you share some screenshots of what it looks like for them? Why do they need to see themselves? What are they trying to do? 

Can you post a screenshot of your actual rule with the code showing? 

Hey @Simmo - Can you shed some light on this? Is this just a weird field type? 

Take a look at the Browse Project permission in the Permission Scheme attached to the project to make sure that the Project Administrator role has that permission. Then also take a look at the Filter for the board to see who it is shared it. 

Hi Gui, We use Kanban and a Pull system to communicate the work and move it through the workflow. If you are not using a pull system, you have to in some way not that the work is ready for QA. So if you want to include a status of Ready for QA, then that is fine. And then have an actual QA (we Test) status. We also have…

Вы используете Jira Cloud или Jira Server? Похоже, вы используете серверную версию. В этом случае необходимо установить отдельное приложение. Кроме того, есть бесплатная версия Lite, а затем полная платная версия.

What does the Audit log say? Can you share a screenshot of when you did the test? Also, you have the full email listed? 

Hi Sanjay - Welcome to the Atlassian Community! Permissions for who can see a project are found in the Permission Scheme for that project. Specifically, the Browse Project permission. Be sure you fit the criteria for it. You also mentioned a Dashboard. Make sure that the Dashboard is shared with you as well as the…

Hi Brent - you might try using Automation For Jira to send the email I know it can send to any email address. 

Ah, that explains it! Thanks for the clarification and support as always @David Fischer !!!

Нет, он встроен в Jira Cloud. Так что вам не нужно ничего скачивать. И, согласно приведенному ниже документу, он работает с Core. https://www.atlassian.com/software/jira/core/features @John McKiernan - Any other ideas on how a Free user can get to the Automation Rules page? 

Correct - but as it walks you through the process you will see that it defaults to a particular status. You can certainly change it (and probably should - but it depends on each status). 

Hi Gui, Workflows are not unique to JSD or Jira Server. They are just workflows. Basically, you should: 1. Edit the workflow 2. Click on the transition you want to limit 3. Click on Conditions in the box that pops up 4. Add a condition 5. Choose one of the User Is In options near the bottom of the list. 

Hi Keri - Welcome to the Atlassian Community! Adding a Flag is Jira's way of denoting blocked work. Or at least that's the way we use it. But it will add a Flag icon to the issue on the board as well as shade it a light yellow. And I guess you could use it (the field is called Flagged) in any query/JQL/filter. 

Hi @Kulbhushan Sharma - Welcome to the Atlassian Community! It sounds like there might be a post function on the transition to Doing that is trying to link the issue to an Epic. Or maybe there is some type of Automation that is trying to fire. I would check the transition from Planning to Doing first to see what post…

Hi Gui, The biggest trap is whether there are statuses in the current workflow that are not in the new workflow. If there are, Jira will want to migrate each status to a new status. But it often defaults to the Done status. And if you are not paying attention, you will inadvertently mark those issues as Done. But you…

Hi Anthony, You might be able to use Automation For Jira for that. Take a look at this post and see Rule #2 as a guide. https://community.atlassian.com/t5/Jira-Software-discussions/3-Jira-automation-rules-we-will-cover-in-our-advanced-webinar/m-p/1398109#M2801%3

Посмотрите, сможете ли вы добраться до этого веб-адреса. Не забудьте заменить "YourDomain" на свой домен. https://YourDomain.atlassian.net/plugins/servlet/ac/com.codebarrel.addons.automation/cb-jira-automation-rules#!/

Hi Phillip - Welcome to the Atlassian Community! This should work using Automation For Jira, but just probably just for Classic Software Projects right now. I believe Automation has a problem with Epic assignments. But it would be populating the Epic Link, not the Epic Name. So the rule would look like: Create Issue…

Hi @PhilSpo , I use this: {{issue.customfield_16705.longDate}} But it can also be written: {{issue.Target start.longDate}} That will give you a result of October 17, 2020.

Hello and Welcome, Jason! We are glad you are here!!

Sounds like you need better users than a new tool. ;-)

Hey Morten - Not exactly sure what you are trying to accomplish. If you do an Edit issue then cite the Due Date field, your code will definitely replace the Due Date with a new value. What do you mean by "I just want a simple way of trioggering an offset/postpone of the due date field."? Can you give us an exact scenario?

Hi Morten - Welcome to the Atlassian Community! Just a note up front - it is always better to create a new question than to post to an existing question. That way more people will see it. When you say: But I cannot do so with: {{now.plusDays({{issue.customfield_20530}})}} I think you have too many brackets. Try this:…

Hi Vadim - Welcome to the Atlassian Community! Can you be more specific? What field does he not see the group in? What exactly are you trying to accomplish? 

Вы можете сделать это с помощью глобальных правил, которые также будут применяться ко всем проектам. Вам нужно быть администратором Jira / администратором сайта, перейдите в Настройки Jira> Система> Правила автоматизации (левое меню). Вы видите это? Чтобы получить доступ к этим настройкам, вы должны быть администратором…

Correct.