Mikael Sandberg Community Champion

Yes, you can disable/delete existing automation rules if you want. Automation is normally used the automate things like if the customer/assignee replies, change the status on the request to the corresponding status. Or to set the assignee based on round-robin, etc.

If you want to use automation my guess it that that is possible too, you just have to add automation to your instance.

Hi @Leelina Dagim, Welcome to Atlassian Community! Yes, there is an option on Data Center to do this using workflow triggers. Workflow triggers allows you to transition an issue when the pull request is merged in Bitbucket, and there also other triggers that can be used based on Bitbucket events.

Hi @Jason Reed, Welcome to Atlassian Community! Here is the corresponding documentation for Data Center. 

Hi @Marcus Hicks, Welcome to Atlassian Community! You could do this using filters, just go to Filters > Advanced issue search. Just note that there is a limit on how many issues that can be displayed, it will only return the first 1000 issues, so if you have more you need to limit your search and use multiple filters…

Currently you can only go into each issue and manually download the form as a PDF or XLSX. There is no API at the moment but Atlassian is working on it and it is scheduled to be available in Q1-Q2 2023 according to their public roadmap.

Hi @[deleted], Welcome to Atlassian Community! There is no option out-of-the-box in Jira to add more fields to the child issues/linked issues list. You would have to get an app in order to do that, like Display linked issues or any of the other apps on the marketplace that can do that.

Click on your avatar up in the right-hand corner and select All workspaces, next click Manage. From here select Plan details and here you should be able to update your card information. 

The best way to do it is to use issue security and then on this one issue open it up so that the outside users can see it. Then create a new project role and add the outside users to that role. You can find more information about issue security here.

Its because of how you constructed your query, it currently says get everything in project FP and FNA, or look for issues with the native label and not not-active. Instead your query should look something like this, assuming you want to limit your search to FP and FNA: project in (FP, FNA) AND (labels in (native) AND…

You can do this with Insight, it allows you to create objects with attributes that you can then add to any JSM request, just create a new custom field and associate it with an object type. The most common use of Insight is to store assets in it, but there are so many other use cases as well.

You always have to go with the highest user count buying an app, so in this case you would have go with 500 users. JSM is a feature of Jira Cloud, so it will have access to apps that you use for Jira Cloud.

Or you could have a project for each customer, but that could be a lot of projects. In that case the first part of the URL would be the same, but they would only have access to a specific project and would not be able to see any other.

If you group your customers in organizations you can restrict it so that they can only see tickets created with their organization, nothing else. If the requirement is also to have different URLs you would either need different instances, or and app like Refined for jira which allows you create different sites.

Hi @David Osborne, Welcome to Atlassian Community! It can be done by using automations, it can send DMs and messages to channels in MSTeams. You may want to ask your Jira admin to add automations to your instance if you do not already have it.

Yes, as I explained in your other question, initiative is just a new issue type and like any other issue type they have to exist within a project. 

Hi @Rajaa Ghani, Welcome to Atlassian Community! All you have to do is create a new board, and select it to be a Scrum board and associate it with the exiting project. 

They have to live within a project just like any other issue types. If you have not already created the initiative issue type you have to do that first, then add the type to the issue type screen used by the project. Once that is done you have to update the issue hierarchy in Advanced Roadmaps. You can do that if you go to…

Hi @Brendan Viljoen, Welcome to Atlassian Community! Yes, that is possible, the parent link field is not limited to only show initiative in the same project as the epic. 

The short answer is no, it is not possible. The board is associated with a filter, and you cannot set a filter that only applies to the backlog and then have a different one for the active sprint.

It can be done using the REST API. The endpoints you are looking for are a combination of Get project paginated, Get project roles for project, and Get project role for project.

You can, but a better option would be to use the list feature to list them, lookup issues will return a list of issues and you can use that to create the list directly in the message like this: {{#lookupIssues}} * {{key}} {{summary}} {{url}} {{/}} You find out more information about using sections and list with smart…

And if you subscribe to Atlassian Access you have access to Insights that shows you active users for up to two years. Just go to admin.atlassian.com and Security > Insights.

Yes, it's possible, have a look at automation which allows you to do it.

You may want to take a look at automation, it allows you to create new issues and copy the information over from the original issue. If you go to project settings > automations you have an automation library with lots of examples.

Automation cannot currently trigger on project creation, but you could do it on say version created. You could then have a initial version that is always created when you create a project. You would have to use REST API calls, since automation in Confluence cannot create a new space, and Bitbucket doesn't have automation…

Yes, it is possible, and you can do this with automation. The first automation would be triggered on sprint started, then use a lookup issues for that sprint and then send the Slack message like this: The second automation would trigger on version released.

For Team '22 it was about $650 if you registered early, and I believe it went up to $850 after that. I would budget for $1000 plus hotel and travel.

You should see the paint bucket if you scroll up until you see the project name up in the left hand corner. If you hover the over it you should see it.

Hi @HG System Admin, Welcome to Atlassian Community! This is expected when you are in a Jira work management project. You can change the background color if you hover next to the project name and you should see this: