Yong Yang Community Champion

Hi @Luisa Morcillo Rehberger Welcome to our Community. Here's a solution for you: 1.Link the two issues between JPD & JSM; 2.Create an automation rule in JSM project Trigger: Issue Transition Branch rule / related issues: Linked Issue (e.g. Types: is idea for) Action: Eidt issue fields or something else in JPD Hope it…

在 Sprint Planning 时，可以查看某个 Sprint 里，分配到每个 Assignee 头上的 Issue Count, Total of Story Points 和 Total of Orginal Estimates，不知道是否是你需要的呢？ https://mp.weixin.qq.com/s/X6vd7gZRdiJ-_GeZ6pgeEw

Hi Sunny, No such functionality in Jira Plans. Sprints are teamwork, not individuals'. The agile teams will decide what or how much you should commit based on their capacity. It's actually complicated when we consider employee leave and other factors like team formation stage. For a specific story, the front-end, back-end…

It seems jira server is not supported by Atlassian anymore @Robert Wen_Cprime_ 

Hi @Aerial Loewen Welcome to our Community. This feature is related to your requirement? https://community.atlassian.com/t5/Jira-Product-Discovery-articles/New-integration-with-Jira-Plan-ex-Advanced-Roadmaps-is-now/ba-p/2841514 By the way, it's not feasible to create issue type hierarcy in JPD currently as far as I know.…

Yes. If you still have any question, I can help you connect product manager of TestRay App. He is a Chinese guy.

Hi @Christian Gräfe Not feasible. But a reminder could be an alternative way for you when an issue is added into an active sprint, e.g. using jira automation rule. Hope it helps, YY Bro 

Hi @Ye Hua Welcome to our Community. Please check if you could access this issue directly in our web browser through {{url}}/rest/api/2/issue/123. What app? Maybe you could raise a ticke to the APP support team. Thanks, YY Bro

Hi @Sunny Liao If you're using Jira Cloud Premium plan, you can configure teams in Plan: Hope it helps, YY Bro

Hi @Diana Arruda Please try this new solution: fixVersion in ({{issue.fixVersions}}) status = Done For the previous solution, could you please raise a ticket to Atlassian Support? I don't know why it doesn't work and it looks like a bug or something we don't know the usage.

Hi @Diana Arruda Please try this new solution: fixVersion in ({{issue.fixVersions}}) status = Done For the previous solution, could you please raise a ticket to Atlassian Support? I don't know why it doesn't work and it looks like a bug or something we don't know the usage. Thanks, YY Bro

Hi Diana It seems there's a bug with the above condition. Could you please raise a ticket to Atlassian Support? I've just got another solution for you: fixVersion in ({{issue.fixVersions}}) status = QA Please have a try and hopefully get what you need 😊

Please use the way as highlighted in red color and let me know the result (better with screenshots too for high speed resolution).

Hi @Jet Thanks for this cool update. It's very clear to show the relationships of delivery epcis (in Jira) and discovery ideas (in JPD) through Plan. I have a question about the Goal. Both epics and ideas can be related to Goals. Should we make the epic's goal inherited from the goal of the related idea? BTW, the Jira UI…

Hi @Martina Bassi I don't think Plans feature is available for JSM Premium only. But we can use JSM projects in Plans for Jira Software Premium or Enterprise plans. Hope it helps, YY Bro

Hi @Diana Arruda Welcome to our Community. I think it's feasible. You could try it like this: Hope it helps, YY Bro

This artical is quite cool to connect Cloud & DC issues. Thanks @Fabian Lim I thought it was using Application Tunnels, but actually Application Link directly.

Hi @elizabeth.mcgrory Welcome to our Community. You meant you can see them in the Backlog and Active sprints on the Board, but couldn't see them in the List View? Have you tried to add them in the List View? Hope it helps, YY Bro

Hi @Carson Sham How about sending those tickets list/table to stakeholders through jsm automation rule at regular intervals? Hope it helps YY Bro

Hi @Janarthanan Selvaraj Welcome to our Community. To meet your requirement, I think you need to switch to the Company-managed project. Then create multiple boards with different Jira issues in board filter to run different sprints as you want. Hope it helps, Thanks, YY Bro

Hi @Philipp von Schulthess Welcome to our Community. In fact, you have already only one single Atlassian account to access all related Atlassian products as shown in your screenshot. Your account was generated when you registered with your email. If you don't want to access all the 3 sites, ask the organization…

Less is more. I think taking the ultimate assingee as the developer who fixes the bug can replace creating a new custom field, a simpler solution. 😊 The person who creating bugs is the reporter, which does make sense. That is, QA is the reporter of bugs. 😊

Hi @Xihao Wang It seems no place to change it. Do you want Chinese translation? YY Bro

Hi @Victoria Luskin I think you could try project = ABC AND (component = X OR issuetype = Epic) Hope it helps, Thanks, YY Bro

Hi @jiw In my actual practices, the final assingee should be assigned back to the developer who submitted for testing. I will make statistics the total number of bugs of every developer based on the assignee field after the bugs are resolved. Hope it helps, Thanks, YY Bro

Hi @Kashif Rahman In JSM, we usually use "Shared with" in the portal to fulfill your requirement. The jira field behind is "Request Participants" and we can add more customer so as to let them notified. Hope it helps, Thanks, YY Bro

Hi @Ralf Rutke Welcome to our community. There's no such function to pin the specific fields like created or updated dates. YY Bro

see my first sreenshot

Hi @Lokesh Reddy Please check if any issue security scheme was added to your instance, making some of the tickets invisible to some of users. If not, according to the error message, those tickets may be deleted. BTW, if you're using Data Center, check if those issues were arhived? Hope it helps, Thanks, YY Bro

Hi @[deleted] Welcome to our Community. Please make sure your board filter includes the sub-task issue types. Thanks, YY Bro