Jack Brickey Expert

Have you tried “Add child issue” shown in your image?

Only Business Projects have the Forms in the sidebar. Note that CMP has Business Projects. I suspect that your project may be SW. If you look in the upper left, as shown in my image, you will know what project type you are using. Note, you cannot change from SW to Business. You would need to create a new project of type…

Company Managed Project vs. TMP - Team Managed Project if you are on server then these project types do not apply.

Ok please explain what you are seeing? if you are using CMP you should see this…

If you are on Cloud using CMP project then edit the workflow and add a Field modified Validator to the transition in question. LMK if you need more details on how this is accomplished.

Yep. You might peruse the documentation to see if you can find the new methods. If I get some cycles I will check another instance to see if it has been updated.

I knew that some changes were rolling out on this area but haven’t seen myself. See if this applies to your instance- create-edit-and-delete-users 

Hi Vallary, I do not understand what you are trying to do here. Can you elaborate?

First understand that you need to create a Jira user account for any external client, these are paid licenses. Then ensure that these users are only in a specific group that you create and that is not associated with any other projects. Finally add this group to the Permission scheme under Project settings for Browse and…

It will be hard to make a recommendation without understanding your requirements of such an HR system. For example if you want a full featured HR system that manages pay paid time off etc. then Jira likely is not the solution for you. However, if you wanted to say manage hiring, on boarding, terminations etc. then it could…

Hi Serge, welcome to the community. So Jira isn’t an employee database first and foremost. Jira does allow for user profiles for any individual that has a Jira account. I’m unclear what you mean by avoid switching between tables documents and accesses.

Edit your first automation and look at the details page. There should be a checkbox to allow the rule to be triggered by another rule. Uncheck this.

Hi @James Farr , welcome to the community. This certainly can be done simply by editing the request types that are displayed. You need to be an administrator for the project to be able to edit this information. Assuming you are go to project settings> request types. In this screen you can choose to remove or simply hide…

In Premium Team is a feature (custom field) of Advanced Roadmaps. In which case you would edit teams as described here - edit-teams-from-your-advanced-roadmaps-plan . However, you are showing as Standard and I am unaware of any built in Team feature. But possibly something that has been recently added that I have not…

I agree with Fabian, you should not try to use a JSM project as a template for a JSW project. Regarding your last sentence about feeding issues between your JSM and JSW project what exactly do you mean? If the idea is that you receive JSM issues that then require software development in one of your JSW projects then simply…

The first thing I would do is prove your theory, if you haven’t done so already, about the request type being “one of”. Add an event log action and record the request tight. Then when you see a failure check that audit log and see what value is recorded. Are use the event log action quite a bit in scenarios where I’m…

Hi Landon, welcome to the community. Unfortunately there is no means of doing this. You will have to go through each place and change.

When you say SLA application are you referring to an addon? I wonder if it has the means of disabling the notification similar to how Automation does so?

Yes would welcome info from log especially.

Please share screenshot of your detail view of a story. 

For this situation please reach out to support.Atlassian.com and select billing. 

In the detail issue view of a story or task you should see an icon to creat child. 

Yes I think it is cloud only issue. 

I suspect that you have a validator and transition screen that results in this screen. If you don’t want that on a specific issuetype you need to create a separate workflow and remove the screen and validator from the transition. Hopefully this makes sense if you need assistance please advise. 

You can use a status to pause the SLA. You can use a scheduled automation to trigger a transition to have it transition out of pending.

Sorry I’m confused are you saying that the image you provided is not what you’re seeing? If that is the case could you please provide an image of what you are seeing? 

In fact, I just saw that there is another post referenced under Related Community Content on this page - Team-Field-not-editable-in-Sub-tasks . It indicates the same.

Got it. So I now see that you are on Premium and Teams is associated with Advanced Roadmaps. disclaimer- I don’t use advanced programs currently. With that said it is my understanding that the teams field cannot be edited independently within subtasks. The reason is that the subtasks are really tightly coupled to the…

It appears that the team field may be a custom field. If you want to use this field on the subtask you simply need to add the field to the screen associated with the subtask.

The key point here is that SLAs apply to the Jira Service Management product not Jira Software. You need to install JSM.