Jimi Wikman

Atlassian Community

This is the first post, and I am very confused what this is and how it connects with Operations...or why it introduces a new design language....

Another great addition to Atlassian teams in the automation!

One of the least useful features I have seen in a while.

This is a disruption for anyone who actually works in Confluence, but maybe if this only shows up if I am not on a live page or in edit mode? Content switching is a killer...

A little confusing that they add this when Jira has announced a similar initiative, but with a different approach...
https://jimiwikman.se/content/writings/stories/introducing-individual-capacity-planning-in-jira-join-our-early-access-program-r2519/

Amassive list of feedback opportunities and research here as well as tons of events!

This is very exciting!

Well... the intention is good, but most organizations have more than 8 groups if you want to color code them, and as people already said in the comments... Uploading an image icon instead is a far better feature than this.

What is "Routing" in this context?

I like it!

Sadly it looks like they are going down the wrong path with this...

This is a very, very interesting concept and the first time I have seen Atlassian actually looking at resource management in any serious capacity! This has been missing since they removed individual time in Plans several years ago!

A very important article that talks about accessibility as a core aspect of design.

This does seem interesting, so I will see if I will have time for it, then I'll sign up.

If I understand things correctly, this certificate was created with some help from @Bryan Guffey !

While the customer and products are not bad per se, it seems strange not to use the power of Assets to build a more capable customer system that we can use for other things as well. It feels like a wasted opportunity to build a field-based customer/product view that has basically no functionality and can't really be extended, rather than port the power of Assets...

This is a great addition, especially for those admins that are not already subscribed to Atlassian Statuses, either through email or through JSM Operations.

This is a great addition!!

Not the worst change, but I think there are more important changes that are needed?

I am not sure about this change because Team managed fields are only relevant in a team managed setting. Since these projects are not used or handled the same way as normal fields, why would I want to see them in administrative setting as the Fields view is?

As an administrator I am never touching fields in team managed projects as they are by definition managed by the teams themselves.

What value is this adding for me as a site or org admin? It only seems to add more clutter to an already cluttered view?

I like this change!

This will be of great help to handle change requests. Now I just want to see if we can automatically create these code freezes from a request using automations ;)

Changed Category to Atlassian General, Jira

Changed Category to Early Access, Jira

Great for App makers, but no fun for the customers that will now get an even more complex licensing situation...

I did not even know there were still anything named business project after the merge last year...

This is a really great article about SLA's that I recommend that you check out!