Benjamin_tmh9yg Community Champion

Hi @Jaime Parks , Thanks for the update. See the response from @Brittany Soinski above. Brittany is from the Atlassian team. Are you able to follow her instructions to get in contact with her team? -Ben

Hi @Mark Stevenson , These are the possible ways you can do it. https://support.atlassian.com/loom/docs/how-to-transfer-admins-when-an-admin-has-left-your-organization/ Hopefully ,your IT org admin is still available to make the updates as mention in the document. Otherwise, the only other option is to raise an atlassian…

HI @Jeffrey Bistrong , Have perform various solution in the past whether putting them in description or notes or some kind of long text field for the sake of retaining information that usually is not use but just in case. Or sometimes there's a team that suddenly wants the field back for ease of searching and narrowing…

HI Kent, Welcome to the community. Haven't encounter this error. I have use provision for a while through various instances but seem to be relatively stable once everything is up and running. The only thing I can think of base on that message is that user already exist outside of your organization and that's why you can't…

HI @Jeanne Howe , You can do this for on-prem application that I know of but not on cloud. On cloud, there's an option to uninstall which you can access as a site/org admin. YOu can do this by selecting the managing the app you want and there's an uninstall button on the top right corner. -Ben

gotcha. Are you using granular scopes? I 've notice that the scopes are become more broken down. Perhaps something is missing. If you are using classic scopes, then is should have been the same. 

Correct. The filter is working they way it should from the screen shot. The project should be there to reduce the scope of the filer. The Filter you have in your JQL screen shot should have a parenthesis around the components statements. Otherwise, what the filter is doing is taking everything with the "AND" together to…

HI @Tobey Hallam , Your Org can set a field scheme for your project to require the component field. That should be possible. As for the filter, it looks right and your filter screen does show the result. What exactly is shown on your board and what type of board are you using? -Ben

Hi @Inclusive Interpreting Thanks for the heads up. Not aware that this has change. According to the documentation, the feature should have still been the same to allow public sharing. https://support.atlassian.com/loom/docs/use-looms-privacy-settings/

Hi @Joe Armstrong , I haven't encounter this particular error. Sometimes I do run into weird quirks and things seem to go away once I clear my cache. Have you also tried exporting something small from notion and see if there isn't any issue with the current file or the data? -Ben

HI @koen , Welcome. What do you man by animation? Are you referring to adding video attachments to your work item? -Ben

HI @Carlos Puente , In order to understandthe behavior, do you screenshot of how your automation get triggers. This would give insight on what is causing your current one your are working on instead of the one before. There has to be something that the automation detected that made it chose the work item. -Ben

Hi @Bunmi Alaka , Then the other option is to match up on the destination side. I would recommend reaching out to atlassian support through their service desk and raise a ticket. Perhaps, there might be something that can be done on the back end or possibly an alternative solution. -Ben

HI @Bunmi Alaka , The accounts usually would need to match up prior to migration. That's the key is uses to map all the objects. Either the source needs to be updated or the destination. Source would be preferred. Ones the importer is done, all the data is mapped to the intended user. -Ben

Hi @Jaime Parks , Would start with support as @Kris Klima _K15t_ has mentioned. Here's some articles in the mean time to see if any of the documented checks can help with your login issue: https://support.atlassian.com/loom/kb/troubleshoot-issues-when-signing-into-the-loom-app-or-extension/…

Hi @Michael Chen - Contractor The message doesn't seem to be related. It mentions can't see this project when you are accessing the Epic. Perhaps the Epic was archived or issue security level was applied to not allow specific users to see that Epic. If either isn't the case, then maybe the quickest route to get things…

Hi @Stephen Finegan Welcome. Based on what you mention, MM permission are set correctly on the system since MM is able to work on the tickets. I would edit the queue and see if there's something missing int the filters. All queues are driven by filters. There has to be something there that is missing his user. -Ben

It depends if you are working with products outside or inside the Atlassian Eco system. If you are using something lie OPsGenie, there's already a built in integration. Using tools outside, regardless of the tool, is to have API and webhooks to create Jira incident and other triggers to automatically transition through the…

Hi @Samyak Dalal , Was there any changes done on your profile or on-call schedule? Are other team members on the on-call list facing the same issue or just you. I checked Atlassian status and the OpsGenie service seems to be stable. 

Hi @Peyton Kuhn , Yes. The customer permission needs to be set to open for email request and customer permission. This way when they create a ticket, their account is already auto created. There is a similar post in this regard:…

HI @David Peoples TPI Welcome to the community! Is bitbucket in the cloud? If it is, then your accounts are already Atlassian accounts. If you want the org on which the confluence is part of to manage those Atlassian accounts, you'll need to be Org admin of that Atlassian Organization. An Org admin must help you or they…

Hi @Stephen Chiponda Here's the documentation to cancel: https://support.atlassian.com/loom/docs/downgrade-or-cancel-your-loom-plan/

Yes. that is key. It will still boil down to the team members willingness. A step further is to hire with that in mind. 

HI @Reserve Evanston , Wait. Are you trying to downgrade or delete your account? IF you are deleting, make sure to follow the instructions here: https://support.atlassian.com/loom/docs/delete-your-account/ IF you downgrading, follow this doc: https://support.atlassian.com/loom/docs/downgrade-or-cancel-your-loom-plan/

HI @Alex Cook , It does sound like JSM is best fit given the context. To pilot your ideas, you can start with a Free JSM subscription or a trial. Then take it from there. If it meets all your needs, then move forward with a paid subscription. That's usually my take when evaluating tools. Need to experiment with them first…

HI @Edward Moxley , I've been working with Atlassian Support for many years ranging from technical to billing. They are fairly prompt to respond. Usually, within a day. If it's a very technical issue, it may take a few days. Sometimes, if it feels a bit long, I just message again and I would get pulse reading on what's the…

HI @[deleted] , Welcome. Let's start with getting some additional details as the other are asking. So, that the community can help isolated what is the root cause and see if there is something that can be address through confluence configuration. Is it isolated to just this page? If so, can others access this…

HI @Duminski Alexander , I don't recall but try using the the read and write jira work classic scope types. If you use the granular, it becomes more tedious. You'll need to pick out the field, values, links, and etc. Hope this helps. -Ben

HI @Giridhar Sripada , Haven't come across specific documentation on it. The only thing I found is this documentation: https://techcommunity.microsoft.com/blog/appsonazureblog/get-started-with-atlassian-rovo-mcp-server-in-azure-sre-agent/4497122 Since you are on enterprise, you might want to raise a ticket or follow up…

Hi @Briana Cervantes I see. thanks for the additional context. That's definitely how it's documented. It just a link to associated confluence page from a particular sales object. Doesn't seem like anything else other then linking to a living doc vs attaching a fix doc.