Fernando Eugênio da Silva Community Champion

@Abdi Dahir , Welcome to the Atlassian Community! You can use the "Status" field and add the "Done" and "Documented" status to your workflow. Then when the tickets assume this status in the workflow, the gadget will be updated and will display "Done" or "Documented". Otherwise, you could use more labels or a custom field…

@Ivan Dowling , Welcome to the Atlassian Community It is entirely possible to make the content bold using Jira Automation. Use this: <b>{{#issues}}{{key}}</b>--{{status.name.toUpperCase()}}--{{"status summary"}} {{/}} See the results: Don't forget: Jira automation supports HTML resources for formatting, so a lot is…

@bjones If you intend to use the request-channel-type as IF/ELSE conditions, why don't you just try using the JQL Condition feature itself to map this. For example: request-channel-type = jira request-channel-type = portal request-channel-type = api request-channel-type = email These are types of values identified by the…

@Brisaida Uceda Rafael , welcome to the Atlassian Community! Puede usar el siguiente contenido HTML para hipervincular la clave de Jira y, cuando se haga clic, el usuario accederá directamente al problema en Jira. Usa esto: <a href="{{issue.url}}">{{issue.key}}</a> Puede cambiar la clave de problema a un valor diferente si…

@Rob Horan maaan, you're made a great job! hahaha Sometimes only a workarounds fix our problems. Congrats!

That is my complete automarion rule:

@Cesar Bastos , please try to replicate this steps Step 1: Even if your Send Web Request is empty, it is possible to collect the sending log of this request through the jira log action. For that, you need to check this box in the Action of "Send Web Request": Step 2: After the "Action" of the Send Web Request you will add…

@Cesar Bastos , can you confirm if this Send Web Request is sent with jira automation? Because even the body is EMPTY, if it has been sent by jira automation you can take the code and/or category status from your web request. Then you can use one of them as a conditional for your automation rule.

@Divya Gadhiraju You need to add jira administrator profile in "Advanced Roadmaps Administrator" permission. This is like a supreme level within Advanced Roadmaps. Add only the "jira-administrators" group Without that, you can actually have the view/edit permission restricted to some plans, as long as the person who…

Apparently this is the format that is configured in Jira. If you want to change this, you must ask your jira administrator to change the date and time settings so that jira will use the format you are trying to import.

@din sys No, this is not possible. Subtask is the lowest level jira has, there is no way you can have a hierarchy below that. If you are using Jira Software Premium, you can add new levels on top of Epic, like Initiative or OKR. But it is not possible to add a level lower than subtask.

@Monica Aguiara Não existe um arquivo exatamente padrão, mas você pode seguir de acordo com essa doc aqui: https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/ Usando as principais colunas e valores com: Summary, Assignee, Reporter, Issue Type, Description, Priority Considerando que…

@Rob Horan Apparently you only need to adjust the date format. This is the import format: DD/MMM/YY This is how you are using it: 9/15/22 And here is how you should use it: 15/Sep/22 Change the month identifier, instead of numbers, use the first 3 letters of the desired month.

uh! my bad my bad: Follow the query updated "Request type" != "CAPEX Request (ISMT)" AND status != "Pending" OR resolution = unresolved AND Queue in iqlFunction("Name = \"Service Operations\"") AND Request type" != "CAPEX Request (ISMT)" AND status != "Pending"

@Ste404 Just use this: "Request type" != "CAPEX Request (ISMT)" AND status != "Pending" OR resolution = unresolved AND Queue in iqlFunction("Name = \"Service Operations\"") This will cause any issues other than "CAPEX Request (ISMT)" in "Pending" status to appear in the queue. Remember that if the request type "CAPEX…

@Cindy Jordan This must be happening because the issuetype Story is not associated with your project. If you are a jira admin, try the following: - Go to "Project Settings"; - In the "issues" section, go to "Types"; - Click on "Actions" and then click on "Edit issue types"; - Search and drag the "Story" issuetype to the…

@Evan Smith Exactly. If you are trying to actually create subtasks in other projects, they can only be created if they have a parent issue associated with them and this parent issue must be from the same project as this subtask. When you see the action of "Create Subtask", you need to define the "parent issue" of this…

@Evan Smith , welcome to the Altassian Community! To have subtasks created, it is mandatory to have a parent issue created for the subtask. If you don't think about creating subtasks in the same project and within the same issue created by the support ticket, you really won't be able to do that. Creating loose subtasks in…

@rajeshsipaiya You need to review your field configuration: Go to "Project Settings" Go to "Issues" Go to "Fields" Click to edit the field configuration. Looking for the customfields are present error and you gonna see some information like a tag "required" in this fields. Change to "Optional" and try again. See more…

If the same user, when opening through the portal, does not want to share with anyone. Other users in your organization will not see the ticket. This is a fact. However, in the ticket, you will also not have this user's organization filled in the field. Please understand: If the "Organization" field has a value, this…

@paulcreedy No, no. Unfortunately it doesn't work like that. If both users are part of the organization, when opening a ticket and sharing with the organization, the other participants can also have access. The only way for you to get the Organization without the ticket being shared with other users, would be to create a…

Maybe the user didn't share the ticket with the organization they belong to, but when sending the email, they added this second person in copy in the email, like CC: I would recommend that you review your email configuration to consider removing this feature.

@paulcreedy There are only two ways to do this: 1: The person in the organization who opened the ticket must choose NOT to share with the organization. When opening a ticket through the portal and if you belong to an organization, Jira will ask if this ticket is PRIVATE or Shared with organization. 2: If the person opened…

Take a look at this: https://jira.atlassian.com/browse/JSDCLOUD-630 https://community.atlassian.com/t5/Jira-Service-Management-articles/Choosing-the-right-approach-to-Customer-Management-in-Jira/ba-p/1970761#M1445

@Gail What could be happening is the following: This particular user does not have any assigned Jira Software or Jira Service Management licenses for Jira to understand SSO globally. She is just registered as a customer of your project, without having a license assigned. So SSO doesn't work so well in these cases, because…

@Reshmi Haridas Uh, it's true! We cannot remove the sprint option that custom field after sprint has been completed. If you are making a clone using the "Clone" option within the issue, you must leave the "Copy sprint" option unchecked. Then the cloned issue will be moved to your new backlog with the sprint field empty.

@Reshmi Haridas , welcome to the Atlassian Community! To do this, just do the following: Go to "Project Settings"; Then search and select "Screens"; On the "Edit" screen, add the "Sprint" field. Go back to the cloned story, in your case to story 2 and click on the "Sprint" field. You can edit the field information,…

@Jarosław Kaczmarek Yeah, hahaha I thought about that too about you having too many organizations and it creates a problem with too many automations. JQL feature doesn't allow to filter Organizations like this: Organizations = currentUser() It also doesn't allow identifying the value per user this way: Organizations in…

@Jarosław Kaczmarek Yes, this is possible using automation's Lookup Issues feature. In short, it will collect an existing Jira base and fill in a certain value. The most practical and functional example in your case would be using Organizations, but it can work with customfield as well. See the automation example you must…

@Jerry O_Sullivan There is no such thing as managing drop down issues in Jira Service Management. The best way to visualize the backlog in JSM projects is by creating Queues and configuring JQL's for filtering the issues you want to see inside these queues. By default, JSM projects already bring some queues for issue…