Fernando Bordallo Atlassian Team

Hello @Thomas Augustinus Your idea to add a custom field that is required to be filled in is correct. The fact that you call it Release or Version will not conflict with the existing versioning functionality available. Just add the custom field to your issue scheme and ensure it is required and limited to a discrete set of…

@Nic Brough -Adaptavist- thoughts?

Hello @Matias Varela this information flow is not supported by Jira. You can use JQL to access the basic user information relative to user pickers (assignee, repoter, custom user picker ...)

Hello @Craig Nunn, A good option would be to use labels or custom fields to define what team works on what issue -> then create separate kanban boards based on a filter that will ensure this split

Hello @jamie tannenbaum , You can create a JQL filter for this in two ways: - IF the sprint you are looking into is not closed yet, you can search for `sprint not in closedSprints() AND sprint in currentSprint()` or - `createdDate >= "xx/xx/xx" AND sprint in ('X Sprint')

Hello @Christine Butler , If you go to the project itself and visit the 'Project settings' link from the sidebar you should be able to see the notifications page. Can you share a screenshot of your nav bar when visiting the project settings? (it should have a grey background)

Hello again @Will May So this issue is known. Currently transitions from a status to itself are not supported in the new issue. There were plans to deprecate these in the future but due to the level of use reported these will be re-introduced in the future. You can follow this…

It depends on how you want to interpret these. I'd describe these the following way: - Related to: an issue that holds a direct relationship to another, due to an overlap of information, scope or outcomes. One would use this link to ensure visibility of all important information to resolve an issue - Derived from: an issue…

Cool! I'll share this with a few colleagues :)

Interesting. @Maxime Nie [Tempo] , any ideas on this one?

Hello @AJ Palmer , You should be able to configure the visibility of the fields and the layout (position) in the issue layout configuration. To access this you can click on the 'Project settings' and visit the 'Issue layout' page (found in the sidebar). There you can find the visual configurations for every issue type: you…

Hello @Jeremy Burton Can you share some more information about at what point in time the auto-filling happens? 

I wonder, how different would this be from finding issues based on a particular sprint? After all a sprint goal maps one to one to a sprint

When you say: some magic happens, what do you mean exactly? Is this that your standard Jira project is built on a query that finds tickets in the JSD project? Please share some details on what you see :)

Hello @FD Moore , I recommend you open a support ticket for this. It something the identity team will wan't to look into: https://support.atlassian.com/contact

Hello @Leena Ravjee , Indeed you can use JQL to filter the worklogDate within a range of time. You can't define `currentSprint()` though. You'd have to manual enter start and end dates. For JQL format, please look into this…

Hello @Will May The only transition that the new issue view does not support is from a particular status to itself. Is this the case you are dealing with?

Hello @Michael Edwards I believe you might find your answer in the thread: https://community.atlassian.com/t5/Jira-questions/Script-Runner-Due-date-Set-Up/qaq-p/868148 👀

Hello again @Hansi test With the existing reports, I don't think you have a direct solution for the problem you are trying to solve. You might be able to look into ecosystem options in the market place for extended reporting functionality. 👀

Indeed! We've all handled an internal broken GPS once or twice :P

🤣

Ah! Good times!!!! That one got me too hehehe

Hello again @andreas_pucko I've attempted to reproduce with the same configuration you shown in the video: - classic project - Chrome - mac - Epics panel open - Quick filter selected - resize the side-pane - select different issues & edit the issues Still can't see the problem reproduced 🤔 See the gif: I would recommend…

;) #1 I believe applies at any point in your career though :D Imagine you work so well you manage to make your job seem too easy ;) (you automate stuff, introduce simple processes that help anyone be able to it up, settle a great new habit in the company that makes the task, just get done naturally). You'd find yourself…

Interesting ... 🤔 I actually live on the opposite of #1: make myself redundant. If I can ensure my work can be delegated efficiently to others I can grow into areas the company had not accounted for me initially and push the companies boundaries. My other rules of life are: #0 Do the best job I can. With this done, I will…

Thank you for sharing this @Brian Hill ❤

Hello @steve.collins , you can find the documentation for advanced workflow configurations here. You will see in the `conditions` sections that permission conditions can be set t allow only users with a certain permission to execute a transition.

You might be able to leverage the velocity chart side by side the burndown chart as they reflect both the total amount of expected effort at the end of the sprint as when the sprint started and you can see the difference there

Indeed. There are interesting views into a future where project configurations and templates are handled in a modernized (ecosystem-style) way with next-gen. :)

Hello @sri.rangineni , the issue you are facing is due to the fact that there are currently two different editor experiences in Jira. The old experience does not support tables. You will find the old experience in the 'global issue creation dialog', transition screens and other non-modernised views.