John Funk Community Champion

Hi Chris, What type of problem are you having when trying to do a bulk change - it should still let you do that for Next-gen projects. The main benefit of Next-gen projects is that they can be managed as a stand alone project, not affected by any other project. And the functionality that is available is very easy to use.…

Hi Guztavo - Welcome to the Atlassian Community! To change the Screen Scheme for a project, you actually need to edit the Issue Type Screen Scheme for the project to change out the screen schemes used by the issue types. You can find more information here:…

Hi Dwight, You can try a filter like: project = ABC and status changed FROM "UAT" TO "DEV" AFTER startOfMonth() That will show all tickets on ABC project that moved from UAT to DEV this month. Be sure to use the exact status names for UAT and DEV. 

Hi @yusuke.yonenaga - Welcome to the Atlassian Community! How are you identifying Company A Staff and Company B Staff issues? Are they all in the same project? Do you have another field that identifies how the ticket applies to which company? 

Hi Scott, See if this document gives you everything you need. https://confluence.atlassian.com/advancedroadmapsserver/configuring-initiatives-and-other-hierarchy-levels-802170489.html

Hi Laura, When you say "the ticket created from Service desk directly go into my project" are you saying they are the same project? And not two different projects? Do you just mean to your board as Marlene is suggesting? 

条件を特定できる場合、または問題をそのユーザーに割り当てるために何が真実である必要があるかを特定できる場合は、自動化を使用して名前でユーザーに直接割り当てることができます。 つまり、この場合、すべての問題が同じ人に割り当てられますか？それとも特定の問題だけですか？

こんにちは @李国庆 Zoe 翻訳者があなたの質問を理解するのに問題があります。 何をしようとしているのか、何が機能していないのかについて、もう少し詳しく教えてください。

There's also this open feature request for showing the Sub-tasks in the Backlog: https://jira.atlassian.com/browse/JSWCLOUD-7992 You should vote for and follow that one. 

Hi @FR Jira Dev - Welcome to the Atlassian Community! What is it actually returning? 

Ah, forgot you were on server - there's a very easy option in Cloud. :-) From your options above, you would probably select Scripted (Groovy) Condition (JMWE app). Choose the field for priority and use == 4 So it will probably look something like: issue.priority.name == "4" Be sure to test it first though. 

Have you verified that is the case? Because the Atlassian documentation doesn't say that for site admins. 

Hi Simas, I see no way to do this with out of the box Jira Cloud. Maybe an add-on like JMWE or ScriptRunner could do that with a custom condition or validator. @David Fischer 

Hallo Eric, Als u de tijd dat het probleem zich in elk van die 22 statussen bevond, niet hoeft te meten, dan zou ik voor elke fase slechts één status aanmaken. Vervolgens kunt u voor elke fase een aangepast vervolgkeuzeveld gebruiken om de huidige stap van de fase waarin het probleem zich bevindt weer te geven. Of u kunt…

Hey Jop - have you thought about just creating a new board for your Business project and not having to move the issues? 

Thanks for the update!

Thanks @Marlene Kegel - codefortynine - Just added a note in the support link for my vote. 

Hey Ray - Sorry, but that is definitely not what a CFD should look like. I suspect that you are allowing issues to regress to the same status it was previously in. In the world of Kanban tools, that will kill any reliable CFD. As the name suggests, it is Cumulative. The word Cumulative by nature/definition can never go…

Not doing anything special this year. I even forgot to wear green - which I normally do. But always a fun tradition. 

You could use something like ProForma Forms in a JSM/JSD project via the portal. This will allow you to display additional fields based on the value of a previous field. You just can’t make the new visible fields mandatory.

Hi Waldemar - Welcome to the Atlassian Community! It is not possible in Jira Cloud to make a field (or fields) mandatory/required based on the value of another field. 

Oi @Priscylla Dantas Batista Você deve ser capaz de fazer isso usando o Automation for Jira. Isso pressupõe que todos esses campos sejam campos do tipo numérico. Crie uma regra de automação para Jira para quando qualquer um desses campos for atualizado. Em seguida, adicione uma nova ação para Editar problema e selecione o…

Hoping y'all can get it connect to Automation for Jira at some point. ;-)

Hi Rohin, The Two Dimensional Filter gadget will only use values that have a set value available for the Axis such as user picker fields or dropdowns/checklists/radio buttons, etc. 

Hi Frank - Welcome to the Atlassian Community! Would a user ever be assigned to a sub-task on that project that was not in the current Sprint? If so, why? If not, then you can modify the query to look like this: (resolution = Unresolved AND Sprint in openSprints() AND Sprint not in futureSprints() AND assignee in…

こんにちは @李国庆 Zoe はい、Automation for Jiraを使用して、プロジェクトの役割に課題を割り当てることができます。 ユーザーの割り当ての新しいアクションを選択し、それを役割に基づいて決定します。 ガイダンスについては、下の図を参照してください。

こんにちは @李　苗苗 はい。CSVファイルの列に配置することで、CSVファイルの問題の種類を特定できます。次に、列をインポートの[問題の種類]フィールドにマップします。

Hi Matt - and Welcome!! I am excited to review Chartio to see what it is all about as I have not used it before. Your questions are pretty large ones and might need a lot more thought than I have right now. But left me say this at a high level. There are far too few canned reports in Jira. And accessing the data through…

Create the new screen with the fields you want to see on that screen. Then add the screen to the Screen Scheme on the project. Then update your Issue Type Screen Scheme on that project to add the Epic as an Issue Type and tie it to the new screen. 

Hi Pete, I simply add conditions to the transitions in the workflow. For example: Backlog > Design > CAB Review > In Progress > Done Include a transition from Design to CAB Review that is a regular transition with no real conditions. Then create another transition from Design to In Progress with a Condition of Priority = 4…