Fabian Lim Community Champion

Hi @Peter Kakris: We can help and we are located in Toronto, Canada. Feel free to look me up in my profile and connect in LinkedIn.

Hi @Matthias Scheugenpflug Try the wildcard searches from this link: https://confluence.atlassian.com/jirasoftwareserver/search-syntax-for-text-fields-939938747.html Regards 

Hi @Keith Schug It's possible that you are not setting the resolution field. Moving a ticket to done and setting a resolution are different concepts in jira workflows. To ensure that they are the same you have to ensure that the resolution is set via a transition screen or a postfuction that sets the resolution.l ti some…

Hi @Florencia Ferrari Another option that you may consider is the auto assign functionally with jira automation. There are options for balanced work, round Robin and random assignments. Check this video tutorial on how to do it: https://youtu.be/hEh3MsoUxho Regards 

Hola Daniela, Most likely, when you started the sprint the story points were not added to the stories and you added story points while you were working on the sprint. The recommendation is to always assign the story points before you start the sprint so that you can have an accurate representation of your velocity in your…

Yes, most likely it's writing to the other custom field. I suggest you rename of one them to avoid any confusion.

- From the rule, it looks like both are transitioning to "Pending Support". Shouldn't one of them be "Pending Customer"? - Also make sure that you can transition between the two statuses

@David Richard, Yes, it should be ok In a project we have different issues types one for dev work (stories, tasks) and another issue type for (ideas). They would have separate workflows and live in different boards one for scrum and another kanban in the same project. Once the idea is approved, you would create the stories…

@Mahima Srivastav, I agree with @Nic Brough -Adaptavist- on this one, but for some reason you want to have a custom field, I recommend the power custom fields plugin that we use: https://confluence.cprime.io/display/SIL/selectIssues It allows you to filter issues with a JQL. You will need some basic scripting knowledge.…

Hi @Mahima Srivastav: I recommend the following plugin: https://marketplace.atlassian.com/apps/1214172/extended-schemes-for-jira?tab=overview&hosting=server It's a life saver if you are trying to reduce the number of options for issue links and resolution options per project.

@Mark Z: When will be available for Data Center? Right now we have to use a separate customfield for original estimates.

Hi @Divya Narula: I would open a ticket with Atlassian support instead and provide them support zip files so that they can investigate further. Regards. 

Hi @sanjana customer Please share the rule details and an image of your workflow and we can help you better.

Hi @Megha P: Check if you have customfields that have the same name as well in your environment with your jira admin. We have encountered issues where customfields have the same name but are of a different type so it doesn't update them. The solution for us was to slightly rename the customfield to identify what type of…

Hola Felix, Una de las opciones es configurar el "notification scheme". En evento "issue created" agrega el rol de "Service Desk Agents". Link: https://support.atlassian.com/jira-cloud-administration/docs/configure-notification-schemes/ La otra opcion es usar jira automation para que notifiquen al grupo de agentes por…

Hi @harsha vardhan: You've done the right checks with conditions/validators/postfunctions/permission. I suggest you manually create a transition from done to to do and see it fixes the issue.

Hi @Vinod Mendem: You can use jira automation to sum up the story points. You can take a look at this video tutorial here: https://youtu.be/60sWD66l19k The actual atlassian post can be found here: https://www.atlassian.com/software/jira/automation-template-library/sum-up-story-points 

@Piotr Gilert: You can find a video tutorial here that is similar to what Bill has shared earlier. It provides you with various rules to keep the story points under an Epic in sync. Link: https://youtu.be/PROcxEOMyGM Thanks.

Hi @Misty Meyers You can refer to this video tutorial for a few automation rules that will help you sump up to any hierarchical level. Link: https://youtu.be/PROcxEOMyGM Instead of branching to a "Parent Epic", you will have to branch out to a "linked issue" with the corresponding link relationship. I hope this helps.

Hi @Guilherme Taschetto: There is a new feature in jira automation where you can now assign tickets to a specific smart value. - Select the Assign Issue Action - In the "Assign Issue To" field select "Smart Value" - In the "Smart Value" field add the smart value {{issue.Publisher}} or {i{ssue.customfield.id}} -> this is…

Hi Gregg, Yes it is possible to move or link tickets between JS and JSM. In our organization we have JSM to submit tickets through the portal and we use automation or Jira automation to create tickets in a separate Jira Software Project. We also use additional automation to keep the tickets in sync. So when a JS ticket is…

Hola, Lamentablemente esta opción no existe en Jira como lo dijo Nic. Saludos

Hola, Out of the Box la funcionalidad no esta disponible en Jira. Creo que vas a tener que buscar otras opciones desde el marketplace. Es nuestra empresa lo que hacemos es poner links en los campos de instructiones que llevan al usuario a un enlace de confluence donde pueden encontra más detalles. Saludos, Fabian

Hi Kamal, It's possible that the fields have a context and you need to add your new project to it. Here is an explanation: https://support.atlassian.com/jira-cloud-administration/docs/edit-a-custom-field-context/ Regards.

Hi @Peter Beck: Most likely you don't have permissions in the project to delete. Even if you are a super admin, you may not have it. Go to the project's permission schema and ensure that the role or group you are on is the item "Delete Issues".…

Hi @Kash Sinduria Answers to your questions 1. No. 2. No 3. Data won't be lost, but you need to ensure that the same fields are available in the new project screens for create/edit/view screens in order to view the old data. 4. When you move the tickets, it will prompt you to map the statuses from the old workflow to the…

@Adam Dulberg I would recommend using 2 rules instead and use this post about calling rules from another rule. https://community.atlassian.com/t5/Jira-Software-questions/Automation-how-to-calling-rules-from-another-rule/qaq-p/1347348 Cheers.

Hola @Julian Rodriguez : Te recomiendo que te contactes con Tempo directamente ((https://marketplace.atlassian.com/apps/1211881/tempo-planner-resource-planning?hosting=cloud&tab=support). Ellos son muy buenos en responder y seguro que te preguntaran que les envies algunos. Saludos

@JH In that case I would suggest the customfield to be a single textfield instead of user. But yes, like @Dirk Ronsmans said, we should have the ability to enter smart values in the future.

Hi @JH You need to use the {{initiator}} smart value to the user customfield. Usually I would use the assignee field, but you could use whatever customfield you have for the actor. Details here: https://support.atlassian.com/jira-software-cloud/docs/smart-values-users/ Fabian