John Funk Community Champion

Hey Jeevan, This looks like an internal list of things for you to do in your instance. Is there a question you have? 

Hey David - what’s the name of the article?

Well done @Fabian Lim !!

Hi Eleni - Welcome to the Atlassian Community! There are many different project templates in Jira that have a variety of "default" issue types and workflows. The point being that you can use pretty much anything you want and can more custom ones if you like. 

Hi Anita - Welcome to the Atlassian Community! You can create an automation rule that creates a corresponding Jira Software issue and links the two. The rule would be based on a condition that uses a field value in the JSM ticket submitted. 

Hi Javier, If you are looking to do this on a board, you could create a second board and add the Quick Filter there. Here is an article to help guide you. https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

Well, just grasping now, but maybe use customfield_11003 instead of the Epic Link name? 

I think it is the only way you are going to be able to delete in bulk, though the other answers work just great for deleting one at a time. 

Can you post the new rule showing the details? And show the results in the audit log? Fields to be added later can just existing in the Edit screen used by the Sub-task. 

Try {{issue.comments.last.author}}

I will start with World Compliment Day and say well done on this post! And dadgum, peanut butter is good! (wondering if there is a two birds with one stone day!). And certainly National Invest in Veterans Week.

No, you are not going to be able to introduce variables to JQL, so that option is out. The performance will really depend on the number of issues that are being returned by each filter. Plus going 4 levels deep like that may not guarantee results like you expect. You would just need to test it out good with a small sample…

Hi Anatolii - Welcome to that Atlassian Community! Unfortunately, no there is not a way to control that. Automation does things in the order it wants to do them. 

Ah, you are probably using a Team-managed project and not a Company-managed project. Components are not available for Team-managed.

Very good, here is some guidance: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/ And, correct. 

Okay, so this is from my original message: For the fields you are copying down values for from the parent, include code like: {{triggerIssue.Custom Field}} where Custom Field is the exact name of the field you are copying the value from. Here is an example:

No, you can't change the type of a project. You have to create a new type. If you have data that you want to migrate between them after the Company-managed project is created. But there are caveats with that. Let me know if you wan to migrate data, too after you get the new project created. 

Hi Sara - Welcome to the Atlassian Community! Has someone renamed the Epic issue type to Feature? 

So in the rule I have above, if it first determines it is External comment, then you could do an IF/ELSE to see if it is Customer or Else not. 

Hi Xavier, I assume you are using a Team-managed project - is that correct? Is so, one solution would be to use a Company-managed project instead. For the more than 100 items, are they all independent? Or could there be some group where you could use a Cascading field instead? The user would select one of a handful of…

Hi Vincent - Welcome to the Atlassian Community! Are you saying you created a new free instance of Jira. And that's the one you are signed into? And you did not invite the other users you see as Team Leads in your image? And you did not create those Projects? Are you sure you are in the instance you created? 

A couple of things. What are you doing in that third Sub-task create? It does not look like the other 2 and appears to be throwing an error. Next, we will need to see the details of the fields when you are creating the sub-task (show the fields and the values you have in the fields for the Create sub-task action. 

Hi Mahanth, Yes it would since you have conditions. Make sure to add a condition for either the Project Role for atlassian-addons or the Group for atlassian-addons, so the actor can transition the issue. 

Glad you are converted! :-) So what is your requirement for "how much work it took"? What is it that you are measuring/want to see? And yes, because they are linked then you can roll up stuff just like you do with a parent. 

Why in the world would you have 100 different types of links??? Create an issue type called Requirement if you want. Then create an issue with that issue type. Then create your Epic or your Story and link it to the Requirement - using Relates to or something like that. You don't need to be that description with the links.…

The audit log will not show the deleted tickets. I would check your permission scheme to see who has the permission to Delete Issues and tighten that up if you have not already. But bottom line is that I have never seen Jira skip ticket numbers in hundreds of thousands of issues that I have been exposed to. I would say…

Well said

If you are getting Done and Not Done counts, it will have to search twice. 

Hi Sirada - Welcome to the Atlassian Community! What happens if you search for Ticket-4 in the search box? I suspect they did actually get deleted, but you were not aware. The other thing might be if you are using issue level security on the project and you just don't have access to the issue. 

Hi Shivani, Currently, radio buttons are not available to add to the List view for Jira Work Management projects. You can find the list of available field types here: https://support.atlassian.com/jira-work-management/docs/customize-your-list-by-adding-or-removing-fields/