Marc -Devoteam- Community Champion

Hi @Eitzaz Haider How would you even see that, you are not controlling the domain users log in with. So no there is no option to achieve this. If you want more control who ends up at your portal, set your portal not to be open for sign up, customers would need to be added before they can use the portal.

Hi @Jacob.Warren Welcome to the community. You specify that the account is still active, does the customer still set a a customer JSM Product (see user details)? 2nd is the user listed as a customer on the JSM portal?

Hi @Saudamini Deshmukh Welcome to the community. Best is to contact Adapatavist (the vendor and developer or Scriptrunner app). I do think, you can only have one behaviour per issue type.

Hi @Ferran Arnaus Garcia No you can't. The settings are user based used. Any user can set the view options available to different settings as they please. The options provided can be set by (except the global product based ones).

Hi @Jorge Colodrero Estrada You need to be a org admin to achieve this. Also see, enable-deactivated-account-to-provide-site-access 

HI @Dave Welcome to the community. Working with Jira, no. You would require a marketplace app or create an automation rule that based on like a set label or component sets a comment on transitioning the issue to Done

Hi @Andreas Springer _Seibert Group_ No I can't say I have. You could try using an incognito window to check, as this could be any other browser plugin causing the issue.

Hi @Antonia This is not possible. See this open feature, JSDCLOUD-12998 

Hi @sunil vemulapalli Welcome to the community. The community is a public open forum, don't specify email addresses or instance url's. You will need to contact Atlassian Support for this action. You need to been admin on a product to raise an issue at Atlassian Support, or have an admin of your instance raise this.

Hi @mtp service Welcome to the community. Whenever you ask for help with an Automation Rule it will help us to help you if you provide: 1. what type of project is this (e.g., company-managed, team-managed, etc.), 2. images that show your complete rule. 3. images showing the details of any relevant…

Hi @Andrew Warren Welcome to the community. This is not temporary. Atlassian has introduced a new GUI. This has bean communicated quite well, al instance admins have been notified on this and it has been as a announcement on every instance. See…

HI @Anastasia Gourina Welcome to the community. So this is not possible, information can be visualised using a request type on the portal where to choose the business application from an assets custom field. So you could, if the information is set as attributes on the Business Application objects. Configure the assets…

Hi @Ferran Arnaus Garcia Only users with the role creator can do this (licensed to project discovery granted) User who are Contributors (only viewers) can't make these changes as they are not licensed to Product Discovery.

Hi @Antonia No that is not possible.

Hi @Antonia Change the Request Types on the JSM project, or create new Request Types on the JSM portal based on the incident work type. See this documentation on differences on Request type and Work…

Hi @Ferran Arnaus Garcia Welcome to the community. What type of project are you using, please provide some screenshots and actions you take to adjust the grouping. But in context, these are visibility options, that a able for a user to be set individually and the latest state is set in the users cookie. A user that…

Hi @Robin Stemmers The user executing the automation role, is that user in a role or groups that is specified on permissions: * Browse * Create * Assign In the permission scheme?

Hi @Danny Anang Tou could look at: "Merge Agent for Jira (JSM Queue & Backlog Issue Merger)" Or can create your own app or look to see what you can achieve by Rovo (creating an own agent). This will probably have a cost component.. But the issue remains user based., user tend to create issues about the same problem…

Please accept my answer as a solution, if my answer helped to solve your request. This will help other community member trying to solve the same. P.S. If the answer is very valuable to you, please share some kudos.

Hi @Rick Pena On using the import, from Jira administration can you use the old importer.? This option is still available on the external system import option in Jira administration.

HI @Mathilde Claeys Welcome to the community. You need to contact Atlassian Support for this. the community is an open public forum.

Hi @Jamiu Adeleke Welcome to the community. Can you access this issue via the GUI? If not, the error is correct, because it means you don't have access to the issue in that project.

Hi @Paresh Magar Welcome to the community. JQL doesn't support the keyword where. What you want to achieve is not possible with ootb JQL, you will need to look at 3rd party marketplace apps like; JQL search extensions or JQL tricks

Hi @Michael Johnson No there are no options to adjust the color scheme in Team Calendars. You could raise an issue to Atlassian on this topic, contact them via https://support.atlassian.com/contact/ 

Hi @Chebbo, Falah [Outlook] This means you don't have a license granted on the instance. Then even if granted a license you could have no access to the page in the space as mentioned by @Mikael Sandberg 

Hi @Charles Wayne In the template section of automation there is even a rule for this, adjust it based on your requirements (status etc...) The template rule is called: "When all sub-tasks are done → move parent to done"

Hi @Chris Holmes Welcome to the community. Contact Atlassian Support There are no options for admins to achieve this by themsleve.

HI @Theresa Barnard Some user triggered this as seen in the history of the issue. has this user triggered this manually or has an automation done this? So it's not a bug, you need to find why this user is triggering this?

Hi @İclal Aslan This field can't be visualised on the portal, this as request types belong to a single project. Request Types are project bound, so even if you create the same request type in every project, the project field can't be used. This as any JSM project is a separate entry on the portal.

Hi @Umang Varshney I can't reproduce this. I can use the connector and even use different JQL clauses on different tabs in a single sheet. If you start with a new file, does it also occur? Can you maybe create a Loom video and connect it here.