Marcos Defina Specialist

Hate to be the bearer of bad news, but this isn't sufficient. What happens when you git push force a rebased/amended commit is that the commit_hashid is refreshed. Atlassian will still have your leaked secrets accessible through repo/<repo_slug>/commits/<commit_id> I'm not sure how long this information would be available,…

Reach out on https://stillwaters.cz/contact-us for a free consultation! We'd be happy to help!

Hi @Deepthi Sajja , I wish I could help you, but more information would be needed on that one. Care to elaborate, let us know what type of fields are missing, perhaps some screenshots of an issue. Have you followed all steps…

Hi @Santhosh kumar TN , Welcome to Atlassian Community. I suggest you to reach out to your instance's Jira Administrator as you will be required Instance Management Permissions. More on: https://support.atlassian.com/user-management/docs/remove-or-suspend-a-user/ Hope it helps!

Hi @Sarah Kriftner Welcome to Atlassian Community! According to this post - It is indeed a legit domain. Check that post out, as it was answered by Atlassian Staff. Bests, Marcos Defina

Hi @sai chinamuthevi , You can use a combination of JQL Functions to achieve that, such as: Sprint in openSprints() AND Sprint in closedSprints() This will give you any task that has been carried over from any closed sprint to any open sprint. But if you have some specific sprint in mind, then just remember that Sprints…

Hi @Ayrat Maksyutov, welcome to Atlassian Community! Done tasks tend to "disappear" once a sprint is over on the Scrum Model. If you have a Kanban Board, you can setup a limit of completed tasks displayed on your Done Swim Lane on Board Settings. Alternatively, you can create a quick filter on Board Settings section as…

Hi @Sahil Godse you can use automation action Create Issue: This will allow you to precisely select whichever field you will add in the new task: Just be mindful of project's screens for the issueType you choose, as there might be required fields you must submit - otherwise automation will fail. Learn more about…

Hi Vasileios Theodorou, welcome to Atlassian Community. Based on your shared screenshot, you should be using Copy from Trigger issue on your Linked Issue Action. You see, Automations works based on a context - When an issue is transitioned to done, your automation starts, and records the transitioned Issue as Trigger…

Lovely initiative! That's how you build a great and long lasting community, by making those who try to help feel good about themselves! Thanks team!

PS: whenever you have troubles like these, feel free to share some screenshots. We're all here to help, but any ill intended person won't have enough information to cause a threat to your organization. Just be mindful of not displaying hardcoded emails, names and addresses on your screenshot and you'll be good.

That's ok Matt, It's quite common to just reuse the code you already wrote in other automations, that brought the initial error to your sandbox test too. It's just the double underscore as highlighted in other comments. I hope that helps.

As answered under @Marc -Devoteam- thread, the problem seems to be a typo on your advanced fields JSON. Having double underscore in between customfield and its id 12657 is causing the failure, as the instance can't understand where to put that information as a customfield__12675 is unlikely to exist, and the required field…

Why the double underscores? seems like this is the problem - your Project Code customfield is required, but you're given something the instance doesn't understand customfield__12657. Fix the typo, and most likely it will work!

Hi @Matthew Valley Welcome to Atlassian community! In order to ensure all fields are submitted to the issue creation, you should make them mandatory in the form software you're using. Once the form is submitted, if there is anything missing, and you enforce the needs of such fields on jira side, all that will happen is…

thanks for sharing the outcome!

Happy to help!

Hi @Phil Beckman Checking more closely your screenshots, I think the problem can be related to altering the fields json with custom_field name "Incident Duration". I'm surprised it worked without throwing a syntax error, but maybe Jira has ways of attempting to match the json value_name to the available fields. I would…

I think you're in the right track, you just need to invert the logic to the else block - as jira works mostly on iteration over tasks, and don't naturally support querying "lack of tasks". Try this same setup but in the else block, with something un-impactful such as log action in the if-true block

Add something silly there, like send an email to yourself, or if you find something even less impactful - that should work

Hi @Brad Prusa , I would try something in these lines: * Run Scheduled event as often as you want (ex: every 15 mins) * Execute an If block with your JQL as first result* If your JQL returns something, then do nothing, and the automation ends * If your JQL returns nothing, then create a task - as you can see in the Else…

It seems you're targeting the wrong task on the Update Action. Your trigger issue, is the one that got transitioned. If you use the Automation Trigger as Issue Transitioned (to Closed), and add all the necessary filter steps to target only the issue type, component, labels, etc you want - then you still need to make sure…

Oh I see! That's ok, the core of the problem I got - only the wrong numbers. You see in the last message of your log, we can see 0 hours for idea - that's what made me believe whatever you're storing inside the loop, isn't getting accessed outside the loop. Try as I suggested, one internal variable, one external - and…

Hi @Jeffrey_Denton I'm not sure if I fully understand the final problem you are facing, please correct me if I'm wrong, but you were expecting to see 20 hours at the final results, right? 10 from Ideas 10 from child Total. If that's the case, I would guess the problem is with declaring your ideaOriginalEstimate inside of…

Long shot here, but is this custom_field included in the view for this project?

Is it too out of the question to suggest a custom issue type (cPIR), and setup an automation to create a new cPIR issue every time an Incident Task is closed? With that you'd have Incident Task as Trigger issue on your automation, and have access to all its fields, including Link Issue To: Trigger Issue. I understand it's…

Ola Ana Paula, Bem vinda a comunidade Atlassian. Essa e uma excelente ideia! Infelizmente esse nao e o canal correto para solicitar melhorias. Acesso esse link abaixo, acesse com sua conta, e crie uma Issue no Projeto Jira Cloud (JSWCLOUD), com tipo Suggestion: Create Issue - Create and track feature requests for Atlassian…

Hi @Phuong Hoang Welcome to the Atlassian community. I think the only problem you will face is your -2M-2w, which isn't a correct syntax. Perhaps you should consider an approximation, such as updated <= startOfDay("-6w"), by simplifying one month to 4 weeks, you can accomplish similar results. Hope it helps!

If you have a programmer at your disposition, you can easily accomplish that by integrating with User management REST API: The User management REST API REST API. Jira offers developers the chance of achieving actions, such as creating, deleting or deactivating an user with your customized requirements. I'm happy to help…

Ola Hildo, bem vindo a comunidade Atlassian. Para conseguir tal acesso, voce precisara entrar em contato com o administrador da sua organizacao. A comunidade Atlassian nao tem acesso ao sua instancia Jira, e nao provemos esse tipo de support - Somos apenas especialistas tentando orientar outros usuarios. Contate…