Fabian Lim Community Champion

Hi @Kyli Kraft Welcome to the community! Are these tickets all from the same Jira Project and you have multiple boards within the project for the various teams? or are they separate projects in a single board?

Hi @Utsav Welcome to the community! If you want to keep it simpler, you can use Jira Automation with the following: - Action: status transitioned to "Blocked" - Conditions: issue type is epic/story/children - Action: Branch to to the parent - condition: if it's not "blocked" - action transition to blocked You can create…

Hi @Jayant Kakkar Welcome to the community! I suggest you open a ticket with Atlassian directly. It looks like a bug in your instance. Posting it here, is not going to help. Good luck

Hi @Arrow Admin You should check in the marketplace for free ones. But the ones that you pay for are worth it since they integrate well with jira automations to add specific checklist for request types. We use smart checklist pro. If you want discounts on plugins, you should talk to Atlassian Solution Partners and they can…

Hola @Analia Busso Parece que la foto no subio. Chequea que el story y los subtasks están completos. Me imagino que el error dice que no podes cerrar el sprint. Saludos

Hi @Javier Peraita Most likely, someone added a new customfield with the same name which Jira allows you to do. I would check that you pick up the right name. Also, use customfield_xxx instead of names in your automations. Regards, Fabian

Si no les pasa a tus compañeros, eso si es raro. Fijate @Luis Gontán Moreno a ver si ocurre con otros browsers en tu laptop. Saludos

Hola @Luis Gontán Moreno Bienvenido a la comunidad! Yo revisaría si el filtro fue cambiado en las configuraciones del board.

Yes, it's not the exact solution, but it should give you an idea. You will probably need a few conditions to check and move the parent to the right status. Like if one of them is in "In Progress" then the parent to in progress.

Hi @gowri goli I recommend using a transition screen where you can add the field only when it transitions. See this tutorial: https://www.youtube.com/watch?v=RIKYX-z4meM 1. Create transition screen 2. add it to the workflow transition and make the root cause field mandatory with a validator 3. Make the root cause field…

Good catch!

that's because the condition is after your action.

check this article: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-insight/ There are a bunch of similar posts in the forum, where people are looping through objects. https://community.atlassian.com/t5/Jira-Software-questions/Create-a-custom-list-object-to-loop-through-Jira-Automation/qaq-p/2171480

Hi @Aabid Akhtar You should be able to see your certificates in here: https://www.certmetrics.com/atlassian/

Hi @marvene Please provide more details. Can you share what you have so far in your automation and confirm that the correct custom field is selected in the workflow to perform the approval? Thanks, Fabian

Hi @Mahesh Swaminathan In order to change issue types they have to have the same workflow. Maybe that's why it's not working. Details: https://community.atlassian.com/t5/Jira-Service-Management/Automation-and-change-issue-type/qaq-p/1324075 Regards, Fabian

Yes.

Hi @Bhanu KN You need a project and I would have 4 different issues types since each RAID items may have different workflows and screens. You can then have a dashboard or Kanban board to manage the tickets accordingly. For each issue type, you will have to have new custom fields. For example for a risk, you want to have…

Hi @PRATHYUSHA DONTHULA Welcome to the community! You can follow this thread here: https://community.atlassian.com/t5/Automation-discussions/Jira-Automation-Video-Tutorial-on-how-to-keep-Parent-and/td-p/1783535 Instead of having all issues change status, you can set it that as long as one of them moves the transition then…

Hi @Edward Moxley Welcome to the community! You will have to create a Jira Service Management Project in your instance that will be running the automation. In your case I would call it something like IT Asset Management Project. From there you can create a jira automation that runs as follows: - Trigger: Scheduled Rule ->…

Hi @Dee from Texas Check this video tutorial that creates tickets to different projects using automation when a jsm ticket is created: https://youtu.be/5Xs8cnDIFBo?si=9a5JiYhOHM0-MzEE Please subscribe and I will continue to finish the series. Regards, Fabian

Hi @Austin Moody Welcome to the community. Unfortunately, you can't out of the box. I suggest you purchase a dashboard hub plugin which allows you create dashboard and have them accessed externally without consuming a license.…

Hi @Ashley Rickard Welcome to the community! If you go to the board, click on "More" and go to customize cards section and you can select what you want to display in the card. Good luck

Hola @servicedesk Bienvenido a la comunidad! Podes postear una foto para ver cuál es problema que tenés? Saludos

You will have to google it somewhere and see if Atlassian posted articles. At the end of the day is what works best for you. Or you can contact Solution Partners who would asses your situation and provide recommendations like Contegix for help.

Hi @Matthew Szoke I would start with request types and use subcategories through custom fields within the request types to further break down. You could also use affected services, components as well. I would avoid using labels since people can make mistakes tagging them and they are case sensitive so "infrastructure"…

Hi @Dominique Clark It looks like it's a plugin. I suggest you contact the vendor to get this one fixed. Fabian

Hi @Osama Al-Areky Make sure that the custom field does not have a context that is blocking you from using it in your FHH project. Also ensure that it's on the Screens for the Create/Edit/View actions. Regards, Fabian

Hi @Boris Krutiy You will have to create a Jira project that has all the schemes for screens, workflows, issue types, etc. which is not a working project but it's used as a template. Then when you create new projects, you can use a "Shared configuration" and select the template project. That way it will keep the key…

Hi @Tech Support SpectrAxe Welcome to the community! As far as I know, there is no configuration to stop jira tickets based on subjects from being created when you set the email configurations. There may be some plugins that may do it for you, but you will have to disable the JSM email requests. The other option is to have…