Arkadiusz Wroblewski Community Champion

@chris sieverts Yes i will say, that are also some form of Solution for your Problem.

Hello and Welcome @Wolf Duttlinger I will keep this on Simple explanation Layer. in JSM, I would read it like this: Work type = the underlying Jira object, workflow, fields, permissions Request type = the customer-facing form/entry point in the portal Work category = the ITSM classification, for example Incident, Service…

@Bhuvanesh Kachave Btw, please try In Private Window and then check if Problem occur.

@Peyton Kuhn Mark Checkbox "Customer can acces and send Requests from the Portal without Logging in" and check again Behaviour.

Hello @Adnan Haider for Jira Cloud, native Azure AD / Microsoft Entra ID authentication via SAML SSO is generally tied to Atlassian Guard Standard. Atlassian’s current pricing and Guard docs list enforced single sign-on (SSO) as a Guard Standard feature, and the SAML setup flow is handled through the Atlassian…

@Siobhan O_Leary Donkin Then it looks like someone from your company who configured and created the instance made a mistake. Normally, when you use an account with the required permissions, you should not have to enter the instance name manually. You should usually see a list of connected apps instead. Atlassian Support

Hello @Bhuvanesh Kachave Failure itself are very Generic and only Atlassian can provide you Information with your Trace ID what happening behind of that.

@Siobhan O_Leary Donkin You noted you are Product Admin Product Admins are mostly not able to raise Request to Support in name of Companies. Request must be putted from Org Admin / Site Admin.

@Dominik Kaźmierski that is a very good finding. If all custom fields / variables go empty inside the comment loop, then the issue is likely context/scope inside the iterator, not the date comparison itself. One thing I would still test is using triggerIssue instead of issue inside the loop, for example:…

100 % Agree :)

@Siobhan O_Leary Donkin * Where to check customer type ? Since you added them under Customers, they are most likely portal customers already. If they do not appear in normal group membership searches, that is expected. * Do they need to be added individually to Confluence? Normally not, if you are aiming for KB access…

Hello @ChristopherChilds for a scheduled rule, Jira does not really have a built-in concept of “current project” in the way you would need here. Once the rule is shared across multiple projects, the scheduled JQL runs against the full rule scope, so if you want project-specific behavior, you usually need to define that…

@Siobhan O_Leary Donkin that additional info points less to a bad link and more to an access mismatch. If the article link is already the proper portal KB link, then I would check whether the affected users actually have the right customer/account type for that knowledge base setup. The main things I would review are:…

Thats great addition. :)

Hello and Welcome @Anujah Siva Organizations are mainly for grouping customers and sharing requests, not really for general broadcast communication. So if a request is shared with an Organization, its members can see that request and get the initial Organization added notification. After that, members usually need to opt…

Hello @QA Team If you want to move a client’s Jira project from one Cloud site to another, I would not use CSV as the primary method. For Cloud to Cloud, the better route is the Jira copy/transfer process. The blank destination dropdown usually means the same account does not yet meet all prerequisites on both sides,…

Tempo making pretty good Time Tracking Apps. Take a look here: Search Results | Atlassian Marketplace

Hello and Welcome @Patric Johansson Agree, but there´s bunches external Apps which Providing that.

Hello @Peyton Kuhn Yep, Open project access alone is usually not enough here. If portal-only accounts are not working, I would first check the global settings, not only the project setting: Customer access must allow customers to create their own accounts Email requests must allow account creation for new customers the…

Hello@Leona Ye It looks like you don’t have a Jira license at all. As you don’t appear to be an admin of this site, please reach out to your admin directly about this.

Hello @Louise Henderson That reply from @Assist usually means the app is installed, but users are still hitting the generic help response rather than a configured request flow. Atlassian’s docs say requests in Teams are raised via the compose box, message extension, or message action. So if @Assist just answers with…

Hello @Waleed Tariq Messeage are self explaining. Only Billing Support can provide you right Answer why you have this Problems. I wish you good luck.

@Krzysztof Borowiecki Your case looks like going into direction legal disputy and only Atlassian support can help you with that about what you talking, @John Funk already provided you a Link. Wish you a good luck. 

Hello @Peyton Kuhn what you are seeing is expected in JSM Cloud. External users can send requests by email without a Jira license, but not really without an account. With the normal email channel, JSM can create the customer account automatically from the sender’s email address. So basically no Jira license needed, no…

Hello @Siobhan O_Leary Donkin This usually happens when JSM knowledge base access and direct Confluence space access are being mixed. A user may be able to view the article fine through the JSM portal / help center, but still get No access if they open the normal Confluence page URL directly. So I would check how the…

@Dominik Kaźmierski from what you shared, I think the issue is no longer the date field itself. Your audit log seems to confirm that issue.customfield_11982 is available as a real date, and that comparisons like issue.comments.last.created.isAfter(issue.customfield_11982) can work. So the more likely problem is the smart…

Hello @chris sieverts that is one of the main differences compared to Jira. In Confluence automation, the rule runs as the rule actor / rule owner, and there is no equivalent to run as the user who triggered the action like you have in Jira. So if the rule says "Rule actor does not have permission to view page", the usual…

Hello @Isabel Mendonça @Marc -Devoteam- is right here. Some apps are a bit of a special / dirty exception during org deletion, and Rovo is one of the common examples. Those apps often cannot be removed directly in the UI, so even if they appear as blockers, you may not see a Disconnect or Remove option yourself. In that…

@Dominik Kaźmierski Please paste Screenshot from entire Automation.

Hello @Álvaro Boza not via a scheme like issue types or screens, no. But yes, in Jira Cloud you can handle this with multi-project or global automation rules, so one rule can cover several company-managed projects. If you copy/export-import a rule, those become separate rules, not one centrally shared rule.