John Funk Community Champion

Hi Arooba, Set the field with a default value of 0. For the existing issues, do a bulk change and set the value to 0 for all of the ones that have an empty value. Then run it again. 

Your screenshot below shows the problem. The boxes that say set resolution. They are what is causing the strike through. Those are not Done type statuses, and you should uncheck those boxes.

Hi Fetu - Welcome to the Atlassian Community! They are different objects for different purposes. What specifically are you trying to accomplish that you can’t?

Hola Richard - Bienvinidos a la Communidad Atlassian! No, no es posible para tender dos nivels de subtarea.

Hi Fawad, Which Cloud version you are running is irrelevant - just consider yourself to be running the latest version because you won't really be able to tell the difference. I would actually create the "projects" as Epics in a single Jira project. Then you have have all of those statuses for the "projects"/Epics and…

You could probably create some type of automation rule that creates the issues until a certain date. It would be sort of self looping that would fire and then stop when it creates an issue with a certain Due Date. You would kick it off and then watch it until it is done and then turn the rule off. I would run it after…

Hi Chuck, Check the history of those two to see if they were marked done at some point and then reopened.

Project Settings > Summary > Issue Type Scheme

Hi Michael - Welcome to the Atlassian Community! So you are saying they are in a project role on the project, but the project does not recognize them? Did you try the Permission Helper for the project to see what it says for something like Browse Project permission? 

This is very exciting! I love the idea about the CEs!!

Hi Tayla - Welcome to the Atlassian Community! Yes, as Dave mentioned, can you share the exactly scenario of what you are doing to accomplish by the "duplicate projects"? Just thinking that this might be accomplished through Epics as your "project" instead of the actual project level itself. The other way might be to…

Can you share a screen shot of the board where you have mapped the "Ready for test" status to the column of the board?

So what happens when you click on the Board link on the left?

So what you are saying is that the tasks must be created in advanced - before the current one is completed. 

Again, that's not standard. That sounds like it is either new work and a new issues should be created to track it. Or it's a bug/defect and should stay in this status until fixed (or another issue created to deal with the bug). 

Great!

You should probably deal with the Due Date in a separate step then. Leave it out of the Clone process. Then add a Condition where the Due Date is empty. Then add an action for Edit Issue and just use the due date field. Then copy it from the parent.

Hi Pankaj - Welcome to the Atlassian Community! See if this article helps you: https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

Hi Marie-Hélène, See if this article helps you: https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

Hi John - Welcome to the Atlassian Community! You should open a support ticket with Atlassian to see any the email address might have been put on the Suppression list for some reason. https://support.atlassian.com/contact/#/

No, I want to see the actual scheme and the values in it. 

Click on Projects, then Create project. Then click on Work management under the Project templates on the left. Then select the top option - Blank project Oh, and I highly suggest after you select the Blank project that you click on the Show more link on the bottom left. Then change the Project type to Company-managed. 

Sorry dude, I am all out of suggestions. You should probably open a support ticket with Atlassian to see if they can help. Please post back here with the solution for future readers. https://support.atlassian.com/contact/#/ Good Luck!

Hi Pavel - Welcome to the Atlassian Community! It might be that someone has either changed the board filter and the new filter is not shared (it is private) or someone might have changed the permissions of existing filters used by the board. 

Hi Rajat, At the bottom of the Send email action, click on More options. You will be able to put in additional information. The email that is sent will show that it came from the Name you have provide although it will have automation@yourdomain.atlassian.net beside the name. If they hit reply, it will come to the email…

Hi Rishi - Welcome to the Atlassian Community! This is just a community of fellow users - no one here will have access to your site to see things. However, in looking at your view, your best bet is to reduce the number of columns in your report. That will make each column wider. Or modify your status names to not be so…

Hi Hizkeel, Why are you moving the ticket backwards? That is not standard Agile practice. 

Hi @Dd Maybe try to click on the 3 dots next to the field and select Copy. This will show a popup with Current Issue in it. Click on those words and change Current Issue to Trigger Issue and change the field to the My Engineer field. 

Hi Adams - Welcome to the Atlassian Community! It will be there, you might just have to scroll all of the way down. You can try putting a space after the 9 but not sure that will help. The other thing is to type in the name instead of the key. 

Hi Sandeep - Welcome to the Atlassian Community! No, no lagging at all. In fact, I would say the fewer schemes you use the better the performance would be.