Marc -Devoteam- Community Champion

Hi @Daniel Landmann There's documentation on how to change your DB. You can find the documentation here.

Hi @Nicola Smith Are you referring to the JSM Service portal or the default Jira Software landing page? JSM Service home, there is no board option. JSW home doesn't have the board menu in the main bar anymore, as ti was in Jira server or DC. You will have to select Your Work menu and select boards or navigate to your…

Hi @Alexandre Gianquinto Welcome to the community. I'm not able to reproduce your issue, on my Cloud instances changing or setting text color is working. If you think there is any issue on your instance, please raise an Atlassian Support ticket, as it might be related to your instance.

Hi @Salvatore Montalto Or did you make a new SLA called TTFR, might be that there is a space in your name, then also a second SLA "with the same name" will be present. @Jack Brickey This could also be a simple reason.

Hi @Albert Marti Based on the workflow related to the issue types on the JSM project, you allow customers to transition, based on the setting to make a WF transition available. On issue view, back-end related, this is only available if you also have Jira Software (if you JSW) to participate on JSM issues. See this table on…

Hi @Jack Brickey You are right the TMP related SLA's are now bundled into one field. I also don't use TMP projects in our setup. I have only 2 TTFR fields, one related to company managed and one to team managed.

Hi @Nicola Smith Welcome to the community? Please provide more detail on what you are experiencing, provide the steps and/or screenshots. This will help community members on helping you with you question.

Hi @Damian Martin As @Stefaan Boes mentions, you can use forms in your JSM project. There is no option for different pages, but you can use sections on the form and based on previous input you can show related fields. See documentation here.

Hi @Salvatore Montalto It seems you are using Team and Company managed projects in your instance. Team managed projects are single containers and don't share information outside the project. Company Managed projects can share there configuration settings within the project on the instance. See the difference on the 2…

Hi @Albert Marti As @Muhammad Moazzam Hassan explains, non licensed JSM users (customers) have no access to the Service project view. Yes it's a provided feature as it provides the option to have non-licensed users able to use your portal.

Hi @Frederik Becker My suggestion is to reach out to Atlassian Support and have them look at the issue. They have access to log information of you instance and are able to see what the issue is. I tried on my Cloud to reproduce your issue, but have not been able to. All our users have access to Whiteboards in Confluence.

Hi @salva garcía raro If you use, the following. {{issue.customfield_10039.value}} or other option {{issue.<name of the field>.value}} Does the compare work, using any of the 2 options?

Hi @Brian Langford Welcome to the community. I think this support article would help you how to install Freshdesk equivalent on the Jira side. See article here: https://support.freshdesk.com/en/support/solutions/articles/50000000067-the-jira-plus-app 

Hi @Alsalaampakistan Please can you explain what the exact issue is? As your summary of your post doesn't align with the description.

Hi @Alexander You could look at this KB article: https://confluence.atlassian.com/jirakb/ssl-connections-fail-from-jira-server-to-external-systems-218269293.html Check the atlassian-jira.log if these failures occur on creating an automation rule.

Hi @s_v_h_haugan You can make your own account on server the Jira admin adn disable/remove the local admin account. Otherwise contact Atlassian via Atlassian Support and see if they can help you out, maybe with a temporary lager license tier on cloud.

Hi @Scott Schellhardt You could look into Opsgenie.

Hi @pratham Hi what was the version of Jira where the DB backup was made from? is your new Jira installation the same version? You can't just use a DB backup file as a restore, the db backup can only be applied to the same version of Jira it was made from. Then you should update you instance to the latest version, as…

Hi @Dreymann_ Thomas I use the properties as well. I usually set the following properties depending on the use cas. If I want to make sue an issue can't be edited on the final workflow status I use: Key jira.issue.editable with value false If I want to make an exception, lets say for group jira admins, I use: Key…

Hi @Felicia ISOLDI Welcome to the community. I made a test page on my Confluence (Cloud) and I added a line in the page (lines are light grey) On pdf export the lines is visible. Are you running cloud or server/dc?

Hi @Ngaire Stratton The explanation from @Sanjen Bariki is correct. Only this is an action the user has to take. Atlassian Accounts are personal, not even an org admin can update this information. The public name is a personal setting. So will have to get in contact with the user and explain the user the actions you need…

Hi @Hoeyer Yes you can you will have to make you Confluence instance available anonymously and also allow anonymous access to the space required. See Confluence set-up public access and make a Confluence space public 

Hi @Lucas de Souza There is no Reopen forms action in automation (I could be wrong), but I can't find it and I have never seen it. You could make an automation rule and use the Web Request action Use a PUT request: https://<<your site here>>.atlassian.net/gateway/api/proforma/cloudid/<<your cloud…

Hi @Cédric Jaduta Welcome to the community. Reading your request partly, but you would need to do this via the API. You would need to create multiple calls to the API Create the custom field using POST /rest/api/2/field and body json as you do. Options can't be given, this is still an option from the GUI on Jira Server.…

Hi @Molly Marshall SLA can't be added to request type, only to the issue view as explained above by @Valerie Knapp . SLA's are triggered when issues, based upon request types are made. SLA information is for agents only. If you need to visualise SLA information on the portal you require an app from the Atlassian…

HI @Paula Martinez Welcome to the community. You would first have to find out what field "custom field 10031" is. Use the JIRA API for this, the call is: https://<your instance name>.atlassian.net/rest/api/3/field/ In the result output find the id 10031. But I expect this is the field for estimation statistics, see the…

Hi @Molly Marshall Welcome to the community No you're not doing anything wrong. The SLA are setup and managed from the SLA settings section. In the request type it's shown as you mention. You can set SLA's as specific fields in a request. SLA in team managed projects SLA in company managed projects

Hi @Boyd Hong If there are no option to find any user, does any user, group or role. I would raise an issue at Atlassian. Support, could be related to your instance.

Hi @Matthew Antoine I can't see faults in you JQL. You might want to pick this up with Atlassian Support.

Hi @Matt Armstrong Welcome to the community. From my experience Conditions and Validators are ignored on a approval step in a workflow. There is an open request for this: JSDSERVER-6342 I have mentioned in this that this also affects cloud and not only server/dc