James Rickards _SN_ Rising Star

Love it. This is a great feature.

Thank you, Firstly, the change from "Issues" to "All work" is really welcomed, I can't express how much time is wasted explaining to new Jira users that an "issue" is not a risk that's gone bad. Secondly, to the developers that wrote this, well done ... nice implementation. Thirdly, to the UX engineers who approved this…

Whilst I have only played around with it briefly in my home lab site. The new UI seems to have been built for 4K monitors as you need more scroll space on the left navigation and more horizontal space for the new above project horizontal navigation. It is difficult to use on 150% scaled1920x1080 15" laptop screens that are…

Thanks for the useful article. I can see you've marked the API as deprecated in your API documentation. It would be very useful to link back to this page from the API documentation so others who find the API doco can understand the reason for deprecation. As it stands it is difficult to know why an API was deprecated or…

My current org does not have enough weight (user numbers) for our complaints to be heard, but happy to add my personal 2c. The new UI fixes some issues such as making it easier to find the operations menu (OpsGenie) without having to go to teams. These deficiencies needed to be addressed; however, I assume that all the UX…

As the old saying goes, if the user can't work things out from what's shown to them on the screen, then the UX design is wrong as it is not intuitive for their audience. In our case, our target audience are engineers. They are all clever folks used to adapting to change. We will thus not be providing any training beyond a…

Please edit this post to provide clarity around impacts to API and Automations, the impacts to JSM and the customer experience in the JSM Portal, and rollout data information.

Great post. It would be good to enhance it to also consider Jira Product Discovery and how it features into gathering feedback and relating it back to a Product Roadmap.

Thank you April. This looks great!

Please don't mis-represent the Agile Manifesto by quoting it without the prefix "Through this work we have come to value:", as this adds the context that both Working Software and Comprehensive Documentation are valued, but the former is more important to a successful outcome than the latter. The subtlety behind the…

This is nice, but there are for more valuable things that Atlassian could have spent time on, given most OS's allow us to open the pages in a second tab and put the two windows next to each other. Why not fix the UX bug where typing `:` causes emojis to be added. Sure ... in some places you press the esc key, but typing…

Having observed around five Jira <--> ServiceNow integrations in past roles, they have all ended up a mess where often they have sync issues, resulting in lack of trust and frustration across the board. In addition, the lack of agility within ServiceNow (changes away from OOTB tend to be expensive to maintain) places a…

I can understand the desire to keep code simple, but current industry practices of large UI changes to a large number of users is to release with a feature toggle (e.g. the labs feature) and gather feedback as to why people turn the new functionality off, then remove the feature toggle but only once they are sure that they…

Looking through this, Atlassian (and @Jehan Gonsalkorale ) are in a damned if they do, and damned if they don't situation. We are all asking for the wrong solution to this problem. The issue is that asking for any default for internal or external comments is short sighted. People will have developed a muscle memory to do…

I just read your article https://support.atlassian.com/jira-software-cloud/docs/what-is-the-new-navigation-in-jira/ It had screenshots of Jira and JSM's new navigation. It said you were bringing consistency, yet in JSM the navigation seems to be in the side bar, but in Jira it's in the new horizontal project navigation…

Fantastic update! You've really addressed most the main issues / concerns with adopting the tool that I've heard from my people. The one remaining concern was around grouping, and bulk re-sizing of shapes. I have a concern around only having a 30-day history as this would not be accepted in government circles. It would be…

This a nice modernization over the older summary screen, and provides a good place to start for newer teams. Yet I would have preferred that Atlassian had invested in improving the existing dashboards features prior to this feature. As it stands, this re-design of the summary screen provides zero value and just causes…

This will be useful, but IMO there are high priorities than HRIS integration such as ensuring that the Teams field plays nice with Jira Automations and can be used on dashboard gadgets (e.g. two dimensional filter) for reporting purposes.

There is an open feature request for this https://jira.atlassian.com/browse/CONFCLOUD-76694 . For similar requests search via. https://jira.atlassian.com/issues/?jql=project%20%3D%20%22Confluence%20Cloud%22%20%20and%20text%20~%20%22Whiteboard%22%20and%20text%20~%20%22Version%22

For me it's more a case of what do I not use Whiteboards for... 1.) Process and other Technical Designs 2.) Team Kanban board 3.) Planning a project through work breakdown structures 4.) Story Mapping 5.) Embedding screenshots of applications and discussing changes. 6.) Visualising information architecture design changes

Tip 1: Don't layer sections as the shapes seems to bind to the wrong section and suddenly get hidden, confusing people. At least it was the case at the time I'm writing this. Tip 2: When Meeting with people, send out the agenda as a wiki page, with spaces to add notes, and an embedded whiteboard. Then when running the…

I 100% agree with @Ignacio Pulgar As a simple workaround I would suggest a global automation for Company Managed Projects that watches for a change to a "green" status without the resolution being set, and an email to the owner of the project so they can fix their mistake. "Trust but Monitor and educate" being my…

Whilst I like the sentiment of this enhancement, it should have been deployed as a new field type, rather than editing an existing field type and this having unexpected consequences.

This is great and a step in the right direction. Will these images be visible on the smart cards on Confluence Whiteboards?

Brilliant.

Vote for this feature Request if you want this feature. https://jira.atlassian.com/browse/JSDCLOUD-12920

IMO, for these managed groups, it makes sense for it to be an admin function, rather than the team doing the rename. For adhoc / unmanaged teams that are not linked then that's different.

I just paste small photos into my board, then have the team members copy their photo and drag it to any cards they take ownership of. To make it easier to find a photo, I have a Frame/Section to describe the team. In that I have a small card with any other info such as links to their profile, their communication…

I'm not quite sure of the outcome you want to achieve? Are you are talking about `sharing` the entire whiteboard to someone? If that's the case, copy the URL to the page, or a link to a specific component or section and send them an email to that link. Why would this not work? Or are you more talking about "adding team…

Seems this is now in the product.