Mikael Sandberg Community Champion

Hi @Marcela Rojas, Welcome to Atlassian Community! You can use sub-tasks to do this, by keeping the main information in the parent issue and create sub-task for each email that you need to track. 

How many users have you added to your instance? Was any of them added with the role of trusted user? Trusted users will automatically have access to all your Atlassian products and count towards the license, but they will not show up in the product access group.

In order to see all the issues that the board filter selects you have to map them to a column on the board, or else they will not be visible on the backlog either. You could use a quick filter to remove them from an active sprint, or better yet, have a process that you cannot add issues that are in Backlog or Scoping into…

Hi @Bryan Collins, Welcome to Atlassian Community! Issues shown in the backlog view have not been assigned to a sprint, and will only be visible on that view. Once you start a sprint, only issues that have been assigned to that sprint will be shown, and they will appear in the column that is mapped to the status that the…

The Edit Object that is in automation currently is for old Insight, at least based on my own research and the information I got from the product team.

If you are referring to the announcement of Deprecating Atlassian account password for Git and Bitbucket API activity then the answer is yes, this applies to everyone, no matter what plan you are on.

You can do this by simply using the if/else condition, no need to create a JSON script to map it. The if/else would look something like this:

Automation doesn't allow you to edit a specific object, so you would have to use the REST API to do it, something like this: The object ID is being used in the call to update the status attribute in this case.

You can share the configuration with an existing project, so you can either create your own template project at you use as the shared project when creating a new one, or use one of your existing ones. Please note that this only applies to company-managed projects. Please have a look at this thread about the same question.

You would have to use a custom field to set the date when the issue moved out of the ToDo status. You can use an automation to set the field when the transition happen, and once you have the field set up you can use that in your report.

To create a new custom field, go to Settings > Issues > Custom fields. Once the field is created you can limit it to only be available for specific issue type by clicking on the three-dot menu and select Contexts and default values > Edit context. See Create a custom field for more information.

If you go to admin.atlassian.com > Settings > Administrators you can add and remove org admins. Once you have been removed as an org admin, another org admin can go to your user and change the product access to remove you from Jira and Confluence.

It should be visible on the portal, because the way Jira handles attachments, not all of them are included in the email notification. If the notification looks like this at the end [G’day, we’re Atlassian.docx] It means that the file format cannot be included in the email so the only way to see the attachment is via the…

To add a new team, open up your plan and then from the View selector click on Teams.

Hi @Richard Hubbard, Welcome to Atlassian Community! When the attachment is added to the request, are you adding it as part of the comment? For the customer to see the attachment they have to go to the request in the Portal and from there they should see it.

You can also reach out to one of Atlassian's partners and let them help you. You can find the list of partners here, https://www.atlassian.com/partners

The short answer is no, you cannot customize what fields from Jira that are being displayed when you open the issue from Bitbucket.

Hi @Lisa Gansky, Welcome to Atlassian Community! By "Done" status I would assume that you are talking about the resolution. The easiest way to clear it is to create an automation that sets the resolution to none, and you need to update your workflow so that when you move out of the Closed status, that you are also setting…

Hi @Elite Vigour, Welcome to Atlassian Community! Please create a new question for this, since it has nothing to do with this one. 

Also make sure that if your board filter is including issues from multiple project you would need to have manage sprint and edit issue permissions in all projects.

Hi @Jill Isaacs, Welcome to Atlassian Community! All JSM projects have the email channel enabled, usually the email is the project key@your-company.atlassian.net, and you can use that or set up your own email and forward it to the address for your project. If you go to Projects settings > Email requests you can see the…

If you want your commit to be available on the remote repository, then yes, you need to push it. There should be a checkbox that allow you to push automatically when you make your commit.

In Sourcetree you have the option to stage specific files, and when you commit it will only include your staged files. This is the equivalent to using git add from the command line. Have a look at Create a file, add it locally, and push it to Bitbucket for a simplified example.

Hi @Greg Davis, Welcome to Atlassian Community! Git stash is an all or nothing command, so you cannot stash just a subset. Git commit allows you to select the files you want to commit, you just have to use git add to specify the files that you want to commit.

It is only the REST API that is changing, the changes do not apply to these fields in the Jira UI and JQL based on the email that was sent out to customers. Here is the announcement on the Developer Community.

Are you using Jira Cloud or Server/Data Center? If you are on Server/Data Center that would explain it, since there is a feature difference between Automations Lite and Pro.

Hi @madsmh, Welcome to Atlassian Community! First thing you need to check is if you have permission to manage sprints. Go to Project settings > Permissions and look for

Hmm, you should have access to the Create Issue action, unless you are on Jira Server and are using the free version. This should do what you are looking for: If you do not want to go the automation route, your only option without getting an app would be to clone the request and then move the clone over to the JSW project.

Hi @Paul Statham, Welcome to Atlassian Community! You could do this with automation and adding a new status to your workflow that can be reached by any other statuses. Then when you want to create an issue in JSW, just move the request to the new status and configure your automation to trigger when that happen. One of my…

Hi @Gopisankar M, Welcome to Atlassian Community! You can select your branch if you go to the Team explorer, or your should see the current branch you are on down at the bottom in the right-hand corner, and if you click on it you will see a list of branches that you can switch to.