John Funk Community Champion

Thanks for the clarification, I misunderstood. Where is the value for this URL stored? If your hard coding it into the email, you ought to be able to put the appropriate HTML around the URL.

Hey Tim, I would actually say this is a great example of having a different status. If you’re wanting to add an optional approval, that would mean a different status anyway, typically. I would just add another status and assign it to the supervisor when the agent moves it to that status. Otherwise, if it’s not needed just…

Is this a Team-managed project, I assume? Did you create the people fields as shared custom fields? Or just independently in the project?

Hi Ruud, Since your workflow allows you to move freely between statuses, I suspect you might have a Condition on the transition to the next status that is preventing Automation from moving it. Check to see if you have Conditions like that then add the Automation for Jira user to the Conditions (or you can use the project…

Hi Venkatesh - Welcome to the Atlassian Community! A Move will simply move that issue to another project or another issue type. But it remains a single issue. A Clone will physically copy that issue, resulting in two issues. 

The "problem" with having total fields and no parent is where do you actually store that? So if you have 5 issues that have a field with dollar amounts in them and you want to see the total, then you need a field to store the value in. So that same field would need to be in all 5 issues. And as Automation fires and the…

Typically what is done is that the parent will move into In Progress when one of the Sub-tasks moves to In Progress. If the work is not actually being done and driven from the Sub-task, there is no reason to have sub-tasks. But, what is the exact scenario that you want to happen and when? 

You can't change the issue type. You will have to delete that one and create a new one with the right level. 

Hi Olivia - Welcome to the Atlassian Community! I am not completely understanding your ask. What is the exact requirement based on the settings of your project? 

Hi Usha, Can you share some screenshots? Mainly of the issue after it’s created with the component and the components set up itself where you are setting the default Assignee.

I always run the migration after hours just so there’s no conflict there. Or if I know for sure, no one is working on the project at the time I run the migration.

@bala katabathuni - I have already described the steps for you to accomplish that with a Premium subscription. You might try the Structure add-on.

Hi Jordan - Welcome to the Atlassian Community! Can you share some screenshots of what’s happening? I’ve never seen that before where the field shows up in the other section after you hit the save button.

Great! You would need that if you are creating the parent at the same time, you are creating the sub tasks.

Glad it helped. And you are welcome.

Yeah, I guess that prevents the form from failing if the field is required and is not on the form. 

Hi Vicky - Welcome to the Atlassian Community! It somehow thinks that the one you created is now the parent for the next one. If the Parent already exists, why do you have a column for Issue ID? And are you mapping that to anything on the import. If so, don't do that. :) Just get rid of that column. 

Well, not sure what you tell you. If you make it required at the Field Configuration level, then that means ALL issues must have the fields populated when you create the issues. Therefore the fields must be on all forms that use that issue type. But if you then make the field optional, the system has no way to know that…

Just make sure you create a Company-managed JWM project. Then the options are there. 

They will still work even if you make some modifications to the template. 

Hi Amelia, This is a Jira Work Management Company-managed project. And yes, you can use those tools with this type of project. 

Hi Chamdarig, You can do that with an Automation for Jira rule (or ScriptRunner). 

Hi Luis, Do you mean JWM? Or JSM? :-)

Hi Santhosh, I I am pretty sure you cannot use subtask issue type with request types, because you can’t create a sub task directly with a request type because there is no parent.

Hi Nabeela, Can you please share some screenshots of what you were seeing? And any errors you are getting.

Hi Sakina - Welcome to the Atlassian Community! By archive - do you mean just remove them from the board? 

Hi Radhika, You can use this: <a href="{{issue.toUrl}}">{{issue.summary}}</a>

Hi Maria, I would open a ticket with Atlassian so that they are aware of what is going on and ask them for a fix. https://support.atlassian.com/contact/#/

So you said the Content Writer is copied from the Epic to the Writing task as the assignee. Why don't you just copy the Assignee from the parent Task to the Sub-task when you create the Sub-task? Another option is to put the Content Writer field in all of the issue types and screens and copy it down when you create the…

Great! And you are welcome!