Mikael Sandberg Community Champion

Hi @Damien Corr, Welcome to Atlassian Community! Unfortunately it is not possible to configure apps to only be available for specific projects (there are a few exceptions). There is a request to be able to do that, let me se if I can find it for you. 

@Shannon Ellingwood No, as far as I know you just have to the event page, no need to add it to your backpack. It should be linked to your Atlassian ID account.

It depends on which pass you are on. If you have the standard pass the content is only available during event days, if you have the all access pass the content is available until Dec 31st, 2021.

Bingo!

Since you have to give them access to Confluence, they will also be able to search for other Confluence users via the People menu or by using the @ mentions feature.

Hi @Joe Chapman, Welcome to Atlassian Community! You are correct, Jira Software just gives you additional features that is geared towards software development. Other than that, everything works the same. Here is a good overview of the differences between Jira Core and Jira Software,…

Yes, it is possible to use accounts that are not using SSO, you can even have a mix of it. We for example are managing all our accounts via Okta, but we do have customers accessing our instance that is not using SSO to get to Confluence. The file size is more based on what plan you are on, it is only Premium and above that…

Unfortunately you cannot define where the destination will be for the placeholder, it is using the sam behavior as when you create a new page, it will end up as a child of the page that are one when you click create.

The text field (read only) can only be set programmatically, either via a post function, listener, Automation rule or any other apps that can set field values.

Yes, licenses are not version dependent, so as long as you have an active license subscription you can upgrade to newer versions.

Here is an example of a security scheme I created for a HR demo project Onboarding is open for everyone, and if I change it to HR the issue will only be visible for the requestor and the HR team.

What controls the access is the Security Level field. If all your issues are following the same workflow you can either use automation to set the field based on the request type, or manually set it by adding the Security Level field to the screen and change it. If the issue that you want to limit access to is using a…

Hi @Henrik Widell, Welcome to Atlassian Community! Follow these steps to create an undefined placeholder page link: * Type [Placeholder Page Name](). This follows the syntax as the keyboard shortcut for adding defined links [Link] (<a href="http://a.com" target="_blank" rel="nofollow noopener noreferrer">http://a.com</a>).…

The 1000 issue limit also applies to Jira Cloud.

Hi @Jonathan Whitford, Welcome to Atlassian Community! You can achieve this by using issue security. Then on the Leave requests you can set the security to only allow for example the HR team and the reporter to see the request. Have a look at Configure issue security schemes for more information on issue security.

Yes, they are either using Server/Data Center, or Viewpoint which allows you to set global URL directs.

Okay, in that case the notification scheme will not help you, since that one will only notify the assignee and anyone watching the request (reporter/customer is notified via customer notifications). You will have to create an automation (project settings > automation) that is executed on issue creation and sends out an…

Hi @carl esposito, Welcome to Atlassian Community! When a new request comes in, do you auto-assign it to one of your agents? Or are you trying to use automation to generate an email to all your agents when a new request comes in? 

And if you want to watch the request for this, add yourself as a watcher on CLOUD-6999 

Hi @Patrick Ng, Welcome to Atlassian Community! At the moment you have to contact Atlassian Support in order to change the URL, there are plans to have this as an option, check out the Cloud roadmap, custom domains are planned for 2022 as of right now. 

@Bill Sheboy Yeah, the create event is a bit different, since not everything is in place when that event happens. From what I have seen so far, the transition event will only trigger the rule after it is completed.

It would only be possible if you set a custom field that identify which transition was used. Automation rules runs after the transition is done (after data is written to the database).

Hi @Hardeep Dhaliwal, Welcome to Atlassian Community! Next-gen and classic projects have been renamed to team-managed projects and company-managed projects, see https://community.atlassian.com/t5/Jira-articles/Two-ways-we-re-simplifying-how-to-create-projects-in-Jira/ba-p/1625982 for more information.

@carlos_marin https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-workflows/#api-rest-api-3-workflow-post

So why would the app not solve your issue? You want to make sure that what you are about to merge doesn’t break anything on your main branch correct? And by default Bitbucket would not allow you to merge anything unless the source branch is up to date with the target branch. So when you do the build in Jenkins you are…

Based on the documentation for Configuration Manager for Jira you can automate the process using their REST API, and it does generate an audit log and you can version control the snapshot that it generates. Not sure if the same applies for Project Configurator, I would check the documentation and also contact the vendor of…

It is not currently possible, but there is a request in JAC to be able to do that, JRACLOUD-75009, but as I mentioned in the comments on it app vendors should be able to do this too. The example I added was Time to SLA, that app allows you to configure which issues it should be available on based on a JQL. 

Looks like the definition has changed for the merge check then. But I found this free app that works around that by adding a merge veto option if the build fails for a specific branch.

So in the repository enable the merge check for successful builds, that will cover your use case. The merge check will only be in play on your master branch and will be ignored on your other branches.

Have a look at Migrating projects to another Jira instance it mention the Project Configurator for Jira that I linked to above.