Mikael Sandberg Community Champion

Okay, are those projects company-managed? In that case you have the two options that I described below, you can either change the workflow if all the projects are using the same one, or change the field configuration scheme and then make sure all projects are using the same one. For new projects you would use the "share…

The short answer is no, in most cases apps are added to all projects, and do not have an option to limit which projects those apps should be visible on. The only thing that I can recommend is that you contact the vendor to submit a suggestion that they add a feature that allow you to enable/disable the app for specific…

Hi @Julia Tomaszewska, Welcome to Atlassian Community! Yes, and no. You reverse the deletion of the priority value by re-adding it as a value. What you cannot do is automatically revert the change of those issues that where changed. For those you would have to create a filter and then use bulk change in order to revert the…

Hi @Joe McCorison, Welcome to Atlassian Community! Are you using a company-managed project or team-managed project? If it is a company-managed project you can edit the workflow and make your fields required when the issue is created, the other option is to make the fields to be always required by going to project settings…

Hi @Max Cacchione, Welcome to Atlassian Community! In order to delete files from the history in the repository (this is the only way to reduce the repository size) you have to use git filter-repo or BFG Repo-Cleaner.

I would recommend that you add a log action step in your automation that logs the values of {{estimatedSubIssues}} and {{totalSubIssues}, that way you can check what their values are and then go from there.

No, the field is visible to anyone that have access to the project, but you have to be an admin in order to make it a global custom field and also add it to the layout.

You could probably use Universal Gadget to do it, since it allows you to create your own dashboard gadget.

Hi @Joel Murav, Welcome to Atlassian Community! What type of project are you using, company-managed or team-managed? If you are in the project it will tell you what type it is down in the left-hand corner. Based on what you have described so far it sounds that it is a team-managed project. If that is the case depending on…

Hi @Brian Trombley, Welcome to Atlassian Community! You could use automation and web request to copy the JSM request and submit it to your third party developers. And then they could set up an automation that updates the JSM request once they are done on their end. 

You can use the external importer to import new issues or update existing issues, so in your case you can import the dates as long as you have corresponding fields on the issue type. 

Hi @l.clipsom, Welcome to Atlassian Community! Yes, you can use smart values for text fields to parse out the data you are looking for. Have a look at the documentation here.

I would probably just remove the cascading field from the request form and then just add it in a Form and make it required. Then just add the form to each request type, I know it may not look the way you want it, but if the fields in the form are required the user would not be able to submit the request without filling…

Atlassian Assist will set the reporter to the user that initiated the request in Slack, and priority will be set to your default value. You can use automation to set the assignee and labels, and if you need to change the reporter and the priority that can also be done via automation.

Hi @Peter Gooch, Welcome to Atlassian Community! The short answer is no, you cannot add the form above the request form fields. The form will always be added to the end of the request type. 

Hi @Hendrik Scheider, Welcome to Atlassian Community! This should be it's own question and then just reference this one. The resolution field is a special one, it will only be required if you add it to a screen. So if you add it to the create screen you will have to set it to a value, but that would also mean that Jira…

Are the two projects team-managed or company-managed? Based on what you described I would think team-managed and in that case you can only keep the data in the fields you have created if they are shared i.e. you created global custom fields.

No, the message on the portal cannot be changed. Then only thing that you can change is the email that is also sent out to the customer.

There is bug reported on this that you can go and add your vote on, AUTO-914 

The Teams field is related to Teams that you see in Jira: Atlassian is rolling out a unification so that the teams in Advanced Roadmap will be mapped and when that happens then the Teams field is linked to that. You can see the announcement here.

Hi @Carbajal, Johann (J.), Welcome to Atlassian Community! The scope can only be changed if you are a Jira admin and it is done from Global administration. 

Hi @Gail Haines, Welcome to Atlassian Community! Currently you cannot copy canned responses to multiple projects or use automation to do it. The only thing you can do currently is manually copy/paste the response between projects. I would suggest that you either use the feedback option in JSW or contact support to suggest…

Yes, that is possible, and you have a couple of options. You can do it by doing a bulk edit, just do a search for all issues that are in the active sprint and then use bulk change to apply the label. The other option would be to use automation and trigger that on when the sprint starts then add the label to all issues in…

I agree, deactivated/unlicensed users should not be shown under Teams. I had a situation were the user deactivation push was turned off between Okta and Atlassian for unknown reason so now we have 200+ users that were off-boarded still showing up under Teams.

Have you tried to expand Comment Visibility and then scroll down? It looks like an update to automation caused an UI issue with the drop-down...

Hi @Donald Curtis, Welcome to Atlassian Community! You probably ended up here because PowerSchool is using an Atlassian product for their documentation. You would probably get a better answer if you post your question in PowerSchool's community. 

The short answer is no, you cannot change the default interval for time fields in Forms, it follows the default settings that Jira has for it's datetime fields.

No, linked issues will not prevent you from completing a sprint. It is only subtasks that have not been moved to the furtherest right column if the parent issue has that will prevent you from completing the sprint.

The JQL that you are using is not returning any results and that is why {{lookupIssues.size}} is 0. {{issue}} is not returning the issue key, you need to use {{issue.key}} in order for it to work.

Hi @jhmcmullen, Welcome to Atlassian Community! Regarding the two invisible boxes/columns, it sounds like you are describing layout, something like this: Those are used to divide your page up in different sections, and you have have multiple layouts on the page. The only way to identify the macros used on a page is to open…