Yong Yang Community Champion

Hi Scott, please see:

Hi @Scott H Welcome to our Community. Please change the trigger to Manual Trigger and then you will see it there. Thanks, YY哥

Could you access this? If not, you may need to create a Support Ticket to Atlassian to release that old name and in the meanwhile, you could use a similar name to proceed your business. After the old name is available, you have the chance to change it to the old name.

Hi @BJ Cardon Welcome to our Community. Could you confirm if the issue creator in JWM is also the Project Lead? If so, it seems to be a product improvement or a bug, which should be reported to Atlassian through Support Ticket. YY哥 Atlassian Certified Expert Atlassian Solution Consultant Cloze Tech, China

Hi @Dusty Brossart Welcome to our Community. I suggest you change the old site name and then reuse that name for the new site because the site name is unique in all Atlassian Platform. Hope it helps you & Thanks, YY哥 Atlassian Certified Expert Atlassian Solution Consultant Cloze Tech, China

Hi @[deleted] Welcom to our Community. It seems you're using Opsgenie App to close alerts or incidents? Could you please share the screenshot you're using? Maybe there's any automation to close incident when you ak'd alerts. I'm not sure. Hope more information is provided. Thanks, YY哥

HI Martinez, I'm not sure about the complete sprint function. However, could I know the reason why you want to use a single board to join JSM & JSW issues? In my previous experience, the delivery team may work on the JSM incidents. In this case, there will be incident issues created in JSW projects, which are linked to JSM…

Hi @Nils Herhaus Welcome to our Community. It seems you're using the incorrect field name. Please see: category = 标准产品 Hope it helps & Thanks, YY哥

Hi @Martinez_ Diego Welcome to our Community. The in-product Insigts feature only works for a single jira project. However, you added two types of jira products. I don't think there's any workaround. Hope it helps & thanks, YY哥

Hi @Karen Knight Welcome to our Community. I have experience to trigger vercel deployment to Production environment through JSM Change ticket's approval. The implementation relies on Jira automation to trigger a webhook. So I think you could trigger Harness automated deployment from JSM side. Hope it hleps. Thanks, YY哥…

Hi @Balaji KM Welcome to our Community. You could use jira automation to add those watchers when issues are created. Hope it helps & thanks, YY哥

Hi @Vara Prasad Welcome to our Community. Would you please take a look at where Build field comes and what it's aimed at? I guess it may be relate to CI/CD DevOps. Then you need to build the codes in the bitbucket/github/gitlab or other CI tools and you will see the build field value change. Thanks, YY哥

Hi @Katie Fye Welcome to our Community. Would you please show us below screenshots? * active sprint * board card config I just tried and it work correctly: Thanks, YY哥

Hi @Mark Moline Welcome to our Community. I think it's the intended behavior. In JPD, creators are licensed while contributors are unlicensed and defined as collaborators of the creators. In Jira practice, if product managers as creators want to involve developers in their ideas, then PMs mention develops through Jira…

Good luck! Vic.

Hi @Vic King Welcome to our Community. Please go to the workflow status property of this issue type. Change to this: jira.issue.editable = true Hope it helps. Thanks, YY哥

Hi @LRobinson Welcome to our Community. When you create a new jira project, you could choose the company managed project like: Please note: you may need a Jira product admin permssion to creat projects. Hope it helps you and thanks, YY哥

Oh, the dependency management in Jira Plan requires us to import multiple projects into a Plan. If we've already built the blocked by links between those jira projects, I think you could see what you expect in the left sidebar of Dependencies. Please just try it.

Hi @Kevin Lu 我看了下，一旦设置了 layout，就无法删除了。可以试试下面这个方法吧： Thanks YY哥

Hi @Todd Winton Welcome to our Community. It seens you're looking for the entry of JSM portal-only customers: Please note: you may need site admin permission to see it. Hope it helps & Thanks, YY哥

Got it. As far as I know, we could add Linked issue field to the Issue Search list

Hi @Naziya Parveen Welcome to our Community. I think you've found a bug, which was reproduced in my side. Please raise a ticket to Atlassian suppport. Thanks, YY哥

Hi @Georg Isenbuerger Welcome to our Community. You may try: issueLinkType = "is blocked by" Hope it helps & thanks, YY哥

To resolve unlicensed agent to update JSM tickets' status?

Hi @George Neshev Welcome to our Community. The text /status has no relation to the workflow status. I think we should go to status switch button to implement it. Thanks, YY哥

Hi @Marisa Skelton Welcome to our Community. It seems no such config for your requirement. I usually press the keyboard shortcuts to switch to Active Sprint with "2". 1=backlog 2=active sprint 3=report Hope it helps & Thanks, YY哥

Hi @Neeta Dubey Welcome to our Comunity. I suppose that you've changed the issue type hierarchy in your Jira Software Premium/Enterprise Plan and the Feature and Epic are in the same level. Please correct me if it's wrong. For Objective (level=2) -> feature/epic (level =1) -> story/task (level=0), we usually use Parent…

Hi @Nitesh Agrawal Welcome to our Community. I think this document should help you: https://support.atlassian.com/jira-service-management-cloud/docs/use-deployment-gating-with-github/ Thanks, YY哥

Hi @Irina Poghosyan Welcome to our Community. Sprint is jira product wide, not project or board wide. So if an issue is in the sprints of multiple boards, then we wil see those sprints in each of those boards. Hope it helps and Thanks, YY哥

Hi @Tomasz Bis Sorry, I haven't got any eperience of integrating with Azure DevOps Rest API. But you may do some research through https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-7.2. Thanks, YY哥