Fernando Eugênio da Silva Community Champion

@Tina.Henry This is a concept that depends heavily on how the team's business rules work. When we talk about issue statuses, we talk about phases that the issue goes through until it reaches its end point. Changing the statuses to use sub-tasks can generate a huge wave of sub-tasks that where using by status, the action…

@Foroud Saraji You don't need to uninstall the product to update your licenses, just go to my atlassian and get the license keys and change them in your environment by going to "Applications". But for your case, as there was a tool version update, I faced something similar and it was because we were using insight and he…

@Alexandra Wilson I recommend you check with who manages users in your cloud environment. Usually these people have system admin access and can access the link I gave you to open the Atlassian support ticket. If you have permissions to manage users, click on "User management" under "Users" and then on your user add the…

@Maristella Botsi Please click "Accept Answer" to make it easier for other users with similar issues to find the solution.

@Maristella Botsi Hahaha Small details that make a difference. If you have any questions, we're here to help :)

@Maristella Botsi , Can you send any picture to our visibility?

@Dawn Lowery You can use the trial period (30 days) to explore Atlassian Acces solutions. If it doesn't look good, you can cancel the trial at no additional cost. But really natively Jira doesn't allow this authentication for portal clients. a workaround would be to make customers active users of Jira and force this…

Yes, it´s possible. This is feasible if you internally edit the "Organizations" and add this customer's organization. This way, he will be able to view the ticket on his portal, filtering the issues that are shared with the organization he belongs to. Another alternative would be to share these tickets with this customer.…

@Dawn Lowery I have the same point. Around here we are evaluating doing a trial of Atlassian Access due to the information we found here: https://jira.atlassian.com/browse/JSDCLOUD-630

@Maristella Botsi For you to be able to share items with the organization, you need to be a registered user as a customer within the organization. See the example: In my test project I have two organizations: Google and Amazon My user is only registered in the "Google" Organization. When opening the request through the…

Please check the following: Access the JSW project; Access your settings and go to the "People" section. Check if your user is registered with some role. If so, check if it's the "administrators" role. If not, click on "Add people", enter your username and assign the role "administrators". Once that's done, still in the…

You can point the issue creation in a new project by clicking on "Project" and selecting the Jira Software project After that, click on "Issue type" and indicate the issuetype that will have the issue created in the Jira Software project. After that, click Choose fields and select the fields you filled in the JSM form to…

@DIEGO CARDOSO , Sendo um relatório por projeto, acredito que o que você consiga extrair de informação de maneira nativa seja criando um filtro e criando algum dashboard no Jira com este filtro. Os relatórios que geramos eles realmente seguem a linha de sprint, mas a depender do relatório que você está tentando gerar,…

@Alexandra Wilson Proforma fields are unique to JSM forms. If you are using Proforma, I recommend that you continue with the use of custom fields from Jira itself and configuring them in Proforma, so you can replicate values for the issue in the Jira Software project (JSW). About automation itself, it is very simple to be…

@Rachid Ahajri Pour les scénarios "Gérer les projets" et "Parcourir entre les projets", vous pouvez inclure le rôle de projet d'administrateur sous "Gérer" et sous "Parcourir", vous pouvez le conserver ou en inclure un autre. Ces paramètres d'autorisation de la section « Autorisations de projet » que nous conservons…

@Rachid Ahajri Pour que seules des personnes spécifiques aient accès à des projets spécifiques, vous devez procéder comme suit : Accéder aux paramètres du projet ; Dans l'onglet "Personnes", enregistrez les personnes impliquées dans le projet et attribuez-leur un rôle de projet : "Développeur", "Propriétaire de produit",…

@Danielle David If you intend to pull service teams and these service users are within a Jira group and are "Assignee" of the issues, you can use a JQL similar to this one: assignee in membersOf("site-admins") AND Satisfaction is not EMPTY AND Satisfaction >= 2021-10-01 assignee in membersOf > Indicates that the…

@Clam Shitanaka Sorry for the delay in responding. As I understand you want to change this sub-task creation screen, correct? Do you really want to change the entire screen or just remove or add new fields to it?

@David If you are part of an organization, when you create a Jira item through the customer portal, you have the option to "Share with an organization" or "Open request privately". The second option indicates that only you and future users with whom you manually share this will be able to see the Issue. The only way to…

@Aamina Reihana Seeing this way, the settings seem correct. I believe that there is some other SLA with similar settings preventing the visualization of this one. We can keep reviewing to help you, plus you can also open a support ticket at Atlassian via the link: https://support.atlassian.com/contact/#/ If it's something…

See another test with the Issuetype "Operations Request" and the highest priority. The value for the time to resolution SLA changed as inserted in the previous JQL, but the time to first response value remained with 2h, as configured in its due SLA.

Hey, @Aamina Reihana Happy to know you managed to solve one of the topics. Under Star to counting conditions for the First Response SLA, what is included? I exactly replicated your rule in my environment and got the following result: Time to first response: Time to resolution: See that I filled in the priority as "Medium"…

@Clam Shitanaka Welcome! This happens because the fields "Request Type", "Due Date" and Release date" are mandatory when creating the sub-task. You can change this by going to the project settings, under "Fields", select the field configuration for Sub-task and remove the obligation for these fields. If these fields are…

@Nate Dickinson If you plan to use the same internal project for external clients, then these external clients will be able to access the other types of requests. But if you need external clients to only see requests that will be useful to them, you can create a new JSM project in your environment and register the clients…

@Aamina Reihana For the other SLAs of 8h, 16h, 30h and 80h use the same IN condition. For example the 80h: issuetype in ("Service Desk", "Awareness Notes", "ECN", "DV/PV", "Operations Request") AND priority = P4/Minor Just apply this "IN" setting to the others and I believe it will work. If this doesn't work, come back…

Hey, @Aamina Reihana I replicated the scenario you are using in the 2h SLA. The error is in the OR condition of your JQL. For SLA's, when it comes to including more than one value for the same field, we use the IN function and not the OR. Try using the following JQL in your 2h SLA: issuetype in ("Service Desk", "Awareness…

@Aamina Reihana To give you a more direct answer, we would need to see how your SLA rules are set up, what JQLs you use, etc. But if one of the SLA's at some point you're using something like: START: Status (Open, Awaiting response, Closed" JQL: issuetype = Story and Status = "Waiting for response". So this should be a…

@Bill Glynn If you created the automation within the global automations, then you can copy it and from there configure it to work in "Single Projects" assigning the project where you want to apply it. If you created this automation within a project and want to replicate it to another, it is not possible to perform this…

@Adam J , There is no way for you to specify exactly the days you want to bring the query in your JQL, but one thing that can help you is to use "StartOfWeek" or StartOfDay in your JQL queries, see an example: If you want the current week to be Mon-Sun, use "startOfWeek(1d), endOfWeek(1d)". If you want the previous week to…

Repliquei a mesma automação que você e no schedule inseri a seguinte JQL "project = SUB AND status = Open AND updated <= startOfDay(-2d)", conforme mencionei no comentário anterior, isso pode te ajudar a resolver o problema.