John Funk Community Champion

Hallo Noah, Ich nehme an, dass es sich hier um ein Geschäftsprojekt handelt, weil Sie das Feld „Kategorie“ verwenden. Wenn ja, besteht das Problem darin, dass das Feld „Kategorie“ noch nicht für Automatisierungsregeln verfügbar ist. In diesem Fall sollten Sie das Feld „Kategorie“ wahrscheinlich nicht obligatorisch machen.…

Hi @N McMahon What status are the issues in which show in the filter but not on the board? 

Agreed - this is the best approach. Create multiple transitions with different names and then use different screens and validators for each.

Hi Mariola, If you look at the ticket in the Agent view, it will say View request in portal right under that name of the person who raised the ticket. If it does not say that, it was not created through the portal.

Hi Titton - Welcome to the Atlassian Community! Let's try to get someone from Atlassian to come help you with this. 

Not the view issues screen, but the Edit screen. 

Hi Renata - Welcome to the Atlassian Community! I understand your question - and no, that process does not makes sense. One, you probably have too big of a team and that should be broken up. Two, you should not have multiple assignees to a single task. Three, you shouldn't try to do all of your work under a single task.…

I understand, and that's what I suggested to you in my first answer. What will not work with that?

Hi @Graphicz - EX00603 - Welcome to the Atlassian Community! Sadly, we will not be able to answer that here. You much contact that company for help. 

This is the Hierarchy - thanks for sending that. But it is is not the Issue Type Scheme. Can you share that please. 

Last question before going to support - Are both of those fields on the Create and Edit screens for that project? 

So the Epic has a value in the Parent field. Is the Parent in the same project? Or a different project? If different, are you sure you have full permissions to that project? Is the rule a single project rule? Or have you included both projects in a multi-project rule? 

Sorry, missed the part about changing the trigger for the parent. So what doesn't work with the latest rule? Also, you can't use {{issue.duedate}} for the Due date because that is the same issue. If that should be the same as the one you are cloning from, you don't need to add that field. If it is set from something else,…

That sounds about right. Just be sure to add a Context to the new fields and not just leave them with a Global context. 

Hey Alex - what did support say? 

Nope, you can't have a sub-task in one project be the child of a parent in a separate project. They must be in the same project. 

Hi Mamatha - Welcome to the Atlassian Community! Can you please share a screenshot of your rule? Also, what type of field is the Assigned Application field? Is it a group picker field? 

Dang, is it Christmas again already?? This year is flying by. Not sure that I ever had a remote controlled toy - car or otherwise. If I did, I really don't remember it. I was more of an electric train guy. 

Hi Vishal - Yes, that is only available for JSM subscriptions. 

Hi Konrad - Welcome to the Atlassian Community! Not sure that I am following everything you are saying, but let's start with the first thing. You cannot create a new Team-managed project based on another project because by nature and definition, Team-managed projects are totally independent from all other projects. So, you…

Is the trigger issue - the one that was just assigned, to be the parent of the sub-task you are creating? And are they in the same project? If not, you can't do that. 

Hi SuneelBabu - Welcome to the Atlassian Community! I assume that you would want to change the Milestone 1 to Done when the Sub-tasks are done. Correct? So do the automation for that first. Then build a second rule that is based on Milestone 1 transitioning to Done. I would actually create Components for Milestone 1 and…

I am wondering if it is the type of field. See if you can add a different type of field and do the same thing with copy from Parent issue and see what happens. Maybe Due Date or something like that. Just make sure there is a value in the Parent issue for that field. 

Can you share the Issue Type Scheme for the project? 

Okay, that's good to know. Let's try this - simply take out the Compare condition and see what happens. 

Hi Nick, Are the users in the Customer project role on the project? 

Hi Addelrahman - Welcome to the Atlassian Community! If you chose the wrong project type and created a Business project instead of a Software project, I am afraid that cannot be converted. You will need to create a new Software project and migrate any issues you have on the Business project to the Software project after it…

This is a work around if you do not have the resolution status as a Done category status. Why are you not doing that?

Hi Tristan, This view is currently only available for Business projects.

You are welcome!