Dave Mathijs Community Champion

@James Richards What kind of "trends" for example?

Listeners may be based on issue events, they are most useful when you want to drive or affect external systems from events which occur within Jira. For this use case, I simply prefer an automation rule above a listener. It's easier set up, you can do it via the UI and automation is designed for these kinds of triggers.

Hi @Kristen Roth , your answer reminds me of the book The Five Dysfunctions of a Team by Patrick Lencioni. Summary: * Absence of trust The fear of being vulnerable with team members prevents the building of trust within the team. * Fear of conflict The desire to preserve artificial harmony stifles the occurrence of…

Aha, thanks for clarifying @Alex Koxaras -Relational- , now that you mention it, never thought of it, clever!

Hi @Kanishk Azad welcome to the Atlassian Community! What are you currently using to define your acceptance criteria? Is it in the definition of your user story? Are you using a checklist? Are you using sub-tasks? Please note there there are no built-in acceptance criteria in Jira Software.

Hi @Edward Quinito welcome to the Atlassian Community! Good question. Actually, the result is the same. I couldn't find a use case (yet) where the result is different. Watching this question as I'm interested in other answers.

Are you using any third-party app that enables this FEATURES search box? I don't have this on my scrum backlog in Server/DC.

I so agree with this one. Meetings are mostly status updates, there are so many asynchronous alternatives available.

Great idea @Kristen Roth I also like to share a summary of my Insights Discovery profile for even more detail.

Hi @Yatiraj Sharma are you able to share a screenshot to get a better view on the issue?

Our team organises a quarterly retro to discuss the health of the team. Of course, this doesn't prevent the team members to raise concerns whenever there are any, whether it is ad hoc, during the bi-weekly team meeting, a knowledge sharing session, a buddy talk, ...

I absolutely agree, #alwaysbelearning! My energy comes from sharing experiences and blockers with colleagues, helping each other getting a different view on the matter.

Hi @IT , this can be done with an automation rule, either for specific project, multiple projects you select or all projects. Issue trigger: Field value changed (Rule is run when an issue's field value changes.)

Hi @Afroz Fakhir welcome to the Atlassian Community! If Due date is a required field set by your field configuration, then you cannot remove it, even when some of your components are on hold. Either the due date doesn't change and you want to mark these issues as overdue, otherwise you change the due date to a future date.…

Hi @Ashley , to my knowledge, this is not possible. Once a field is added to the Edit Issue screen, the pencil will show up to the right of the field once you hover over it. The EDIT button will show all editable fields in one screen.

Thanks for sharing the new practice, will apply it tomorrow!

Hi @Manju Rawat welcome to the Atlassian Community! When you add the Issue Statistics gadget the Statistic Type dropdown list should list all available fields. Which system/custom field are you trying to select?

If you're not a board administrator or a Jira administrator, you cannot know which filter is being used. Please have one of those people confirm this for you.

Hi @Sally Evans a Kanban Board is always based on a board filter (and a sub-filter if applicable). This filter shows the related issues for the board. If you are a board administrator, just check the board configuration to see the used filter.

Hi @Ashima Bhatia , please note that Color Custom Fields (if that's the app you're using) has no Data Center approved version.

Hi @Mohammad Aljumaa , welcome to the Atlassian Community! I suggest to submit a support request with Atlassian for this issue as the error message is very generic.

Hi @Andy Heinzer , I'm currently trying your instructions, but Jira won't simply allow me to create the a user with the same username in the Jira Internal Directory if it already exists in the external directory. Any workarounds?

Hi @Tom Lister , yes, I've synchronised manually.

Well, it's either overdue or it isn't, whether you're using a Date Picker or a Date Time Picker. If your Due Date (System Field) is October 27 and it's October 28, then it's overdue If your Due Date Time (Custom Field) is October 27 12PM asnd it's October 27 1PM, then it's overdue. Question: Have you actually created a…

Hi @Lorenzo Paoletti welcome to the Atlassian Community! A Roadmap is a future view per definition, it outlines the initiatives, epics and features in the pipeline. So it doesn't make sense to show (very) old done issues. Besides, that would clutter your roadmap after a while. The Epic issue detail view will always show…

So it's a date picker, you cannot choose a Time. You'll need to create a new custom field with type Date Time Picker and use it as due date.

The system field Due Date has the Date Picker format, so no hours can be selected. I see that your field name is Due. Is this a custom field? What type is it: Date Picker or Date Time Picker?

Then the Due date field needs to be either on the edit issue screen or on a transition screen.

Hi @Sergej Kalva welcome to the Atlassian Community! You'll need the Schedule Issues and Edit Issues permission in the project where you would like to edit the due date. Please check with the project lead if this is the case.

Hi @franck_amaury_mbda-systems_com , I don't see any reference to this feature in the Data Center Roadmap. So don't expect it.