Mikael Sandberg Community Champion

Hi @dnzhu, Welcome to Atlassian Community! One way of doing it is to use components, for example project B and project C. You can then set up the boards in project B & C to look for those components in project A. Once your requirement analysis in project A is done and ready to split it into stories just add the…

The checkbox should appear once you selected the template and company-managed project. It is on the screen where you name the project and set the project key. If you select team-managed project you will not see this option.

Hi @Priyadharshini Ammu, Welcome to Atlassian Community! All boards are using a filter to figure out what it should display on the board. So if you have issues with a specific label that you want to display on a board, all you have to do it change the filter. Then on the board that you do not want the issues to show up on,…

They get the notification because they are either watching the space your page is in, or because they are watching the specific page. You can either publish your page edits without notifying watchers, or if you are the space admin you can manage the watchers, just click on the eye icon. You can find more information about…

They can, but it requires that they have access to your Jira instance and will count towards your license. It is only JSM that allows non-licensed users to submit requests.

Automation should be able to do a lot for you. One of my teams is using JSM for as an intake, and once they decide to work on it they move it to Approved. This will trigger an automation that copies information from the request and creates a story in their internal project.

You could use the REST API to get the projects and corresponding repos, but you would have to clone each one and then run the Git command on the clone. 

You should be able to transition it to Closed and then to Reopened, unless there is a restriction on who can move the issue to closed. You may want to check with your Jira admin if you do not see the Closed transition.

Was the SLA added or updated before or after the request/issue was created? 

Hi @Shirlene Schofield, Welcome to Atlassian Community! It all depends on how your workflow is set up for the Bug issue type. If you look at your workflow you can see if there is a transition that will reopen the issue or not.

The article you referenced is only for Data Center. Bitbucket Cloud does not offer a backup solution, but the easiest way to do it would be to just to a git clone --mirror of your repositories and run that on a schedule. You can also have a look at this sample backup script for Bitbucket…

You could use an Integration Platform as a Service (iPaaS) to do this. We have a room for peripherals that employees can request, and once the request is approved we have an automation that sends a web hook to our iPaaS system (tray.io) that adds access for the employee to that room for an amount of time. We are thinking…

Check your customer permissions, make sure that they can "Customers can search for other customers within their organizations, or manually enter the email address of other customers within their project" that will allow email addresses in the To or Cc to be added to the request.

You should be able to do that with an automation and by checking the request participants field, when you use an email alias the alias will be added to that field.

A good use case for the self-transitioning can be that you need something to happen before the issue can move forward. I have used it for Risk Assessment where the issue was not allowed to moved forward unless the CRB risk assessed the issue first. Because you are using a transition you can control who can perform that…

Hi @harleen singh, Welcome to Atlassian Community! If you provide a screenshot it might be easier to understand what you are referring to, but my guess is that you are talking about the different Statuses. This is based on the workflow used for the issue type, and is either configured by your project admin or Jira admin…

No, select lists cannot be configured to show different data based on the request type. The context can only be configured by project. You could probably do it with an app, the one that comes to mind is Elements Connect and use an external database and configure it to populate the select list based on the request type.…

You can also use Git filter-branch to remove the file. These are the commands for that: $ git push origin --force --all$ git filter-branch --force --index-filter \ "git rm --cached --ignore-unmatch <em>PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA</em>" \ --prune-empty --tag-name-filter cat -- --all This might be the fastest…

Yeah, enabling Git LFS after committing large files will not help, unless you remove those files from history first. I have used BFG Repo cleaner in the past to clear out the repository from large files before moving them to Git LFS. Atlassian has a really good guide about Git LFS that you can find here.

Hi @Colton Carnevale, Welcome to Atlassian Community! The color you see is tied to the category of the status, and those colors are hard coded and cannot be changed. 

Hi @[deleted], Welcome to Atlassian Community! assignee = currentUser() will do the trick for you. 

What command did you use when you tried to remove the file, just the regular git delete? That will just remove the file from that point on, it will not remove it from the history. In order to remove the file from history you have to do this if the you added the file in your last commit: $ git rm --cached<br>$ git commit…

Hi @mmeyer, Welcome to Atlassian Community! It is only JSM projects that has the request type, JSW do not have this feature. You could use then new Jira Work Management, it allows you to create a form that the user can fill out as a simple intake form. You can find out more information about JWM here,…

Hi @john okerlin, Welcome to Atlassian Community! Atlassian has renamed next-gen projects and classic projects to team-managed and company-managed projects, and you can find out more information about it hear, What are team-managed and company-managed projects 

Check the filter that you have on the board, it could be that it is filtering out the Done status.

@Amine Maghrebi the link should work now, for some reason a space was added at the end of the link. No, there is nothing you can do to change when the emails are sent. Your option would be to turn off the notification scheme and instead use an automation rule, since that one will send the email right away.

Hi @Amine Maghrebi Welcome to Atlassian Community! Email batching is turned on by default in the Cloud, and you cannot change that. Have a look at this thread regarding the same question, Is the Batch Email Notifications feature available in Jira Cloud?

@Katelyn Botts No, your customers would still need a license in order to access Jira Work Management and Jira Software projects. It is only Jira Service Management that allows customer access without a license.

Hi @cecilia, Welcome to Atlassian Community! Yes, this is possible. What you have to do is change the permission scheme(s) that your current projects are using so only users belonging to a specific group or project role can browse the project, I would recommend using project roles, you can then control it based on the…

Insight is now part of Jira Service Management (as of March 31, 2021) and the app on Marketplace has been removed, and will be end-of-lifed on March 31, 2022. In order to get access to the new Insight you have to be on the JSM premium plan. I would contact Atlassian support to see if there is anyway to add back the old…