Mikael Sandberg Community Champion

I'm sorry about that, but based on their website they are based in Russia, so you may have to wait for a solution to this for a bit more. Based on the information on their website their Helpdesk is currently offline.

Have a look at this Troubleshooting guide for issues connecting to the Marketplace, https://confluence.atlassian.com/upm/problems-connecting-to-the-atlassian-marketplace-273875718.html

Have a look at this thread that Planyway created, it is also linked on their website, https://community.atlassian.com/t5/Trello-discussions/Planyway-is-slow/m-p/1712055#M1901

I heard back from Atlassian Support and they could not see any bounces on their end. You may want to check that the user not receiving the email isn't filtering it, and that the Approval required email hasn't been disabled.

Yes, if you have create issue permission in the project you can do a bulk import using the CSV Importer. Just go to Filters > Advanced issue search. From here just click on the three dot menu up in the right-hand corner and select Import issues from CSV and then follow the on-screen instructions. You can find more…

You may want to contact the vendor for the app and see if anything is going on on their end. Have you tried using an incognito window and see if the issue persist? Also try clearing your browser cache from all time and see if that helps.

I had a similar situation happening, and the cause was that when the notification was sent from Jira it bounced, causing the receiving email to be added to Atlassian's bounce list. I have notified the Atlassian Support team that is on here, so hopefully they will be able to help you out.

You have two options, you can either create an automation that updates the resolution, or you have to modify the workflow to create a circular transition that sets it. I have used both options in the past, and I prefer the automation since you do not have to change the workflow.

Do you have ssh set up on the Windows server? You would need that in order to access it from a Linux terminal. Also not that Bitbucket is a web application, and only admins should access the server directly. There is an app that gives you a CLI interface, Bitbucket Command Line Interface (CLI), but it mainly from admin…

Hi @Max DiOrio, Welcome to Atlassian Community! This can be done, but you would need be on the JSM Premium plan, that gives you access to Insight which allows you to get a visual view of the dependencies between your services. 

Hi @Denisse Leos Espinosa de los Monteros, Welcome to Atlassian Community! Atlassian does not have sales people, but you could contact one of their partners, and they will gladly help you. You can find all the Atlassian Partners here, https://www.atlassian.com/partners 

labels = my-label or labels in (label1, label2) is how you filter based on a label.

As @Jack Brickey mentioned, this is up to you and your team. The affected services is linked to Services, which allows you to set dependencies to other Services and also add incident responders (linked to Opsgenie), Change approvers (allows you to add them as approvers if there is a change request affecting the service),…

Not from within Jira, you would have to check the release date of the version via REST API, a call to Get project versions can get the release date.

Hi @Isabel Mangan, Welcome to Atlassian Community! As you have discovered, what you are trying to do is not possible to do, since the automation cannot check its own audit log as part of a condition. I would consider doing this check on the side that is triggering the web hook if possible. What is triggering the web hook…

Hi @chirayu0104, Welcome to Atlassian Community! No, you cannot inject javascript into a custom field. But you may want to take a look at Forge which allows you to create apps that extend your instance. The link includes examples on how to add your own custom fields. There is also a dedicated Atlassian developer community…

A good overview on how the screens, schemes, and fields are related can be found here, Project screens, schemes and fields (yes, the document is for Server/Data Center, but it works the same on Cloud).

The board name is not associated with your issues, what you see on your boards is based on a filter. So what you would have to do is create a filter that only shows issues that is part of an active sprint (Scrum board) or are in specific statuses (Kanban board).

You are correct, boards are configured to show issues based one the filter that the board is using. You have the option to change the filter so it brings in issues based on a label or any other fields. Your other option is to create the filter first, and then create a new board and when doing so, set it to use the filter…

The way I did this was by adding a Waiting for Approval status in the workflow, and when you transition to it the agent has to enter the approvers.

Do you have multiple fields with the same name? The few times I have run into this issue I solved it by using the advanced option to set field values and used the custom field ID instead of the name, since the name is not unique.

And the only way to upgrade your existing (legacy) projects would be to create a new project and then move your existing requests over.

Hi @Sandi Slavko, The new JSM project you created is based on the ITSM template, which is based on ITIL where you have 4 different types of requests. You also see the integration to Opsgenie that is now part of JSM (Alerts and On-call menu options). 

@Nir Malchy You're welcome! And I hope you have a good weekend too!

@Roberto Miasack If you are using server you can only replace labels, see this KB for more information, https://confluence.atlassian.com/jirakb/how-to-delete-a-label-in-jira-297667646.html

Yes, that should work.

I do not see a smart value that would get you all the emails within an Organization, so I do not think that is possible at the moment. But since it is an option in the legacy automation, my guess is that Atlassian will implement something similar in the new automation.

You should be able to trigger it using the Field value change trigger and then check on the field Organization.

Unfortunately not, and you can read more about the decision here, https://support.atlassian.com/jira-core-cloud/docs/what-is-the-new-jira-issue-view/, but it basically boils down to that once all customers are on the new view they can release bug fixes and improvements faster.

Note that this only apply to company-managed projects, if you have a team-managed project you cannot make the fields required.