Welcome Wednesdays: Product suggestions you're passionate about?

[Dave LIAO]

Hello Atlassian Community! 👋 It's time for another Welcome Wednesday!

Have you been an Atlassian user for long enough where you were looking for a product feature and found out it didn't exist? Or find a bug that bugged you?

Have you ever found a product suggestion or bug report in Atlassian's public bug tracker? (Did you know they have one? Many folks call it JAC! Because its URL is https://jira.atlassian.com )

If so, what suggestion or bug do you really wish Atlassian would address, and why?

[Arkadiusz Wroblewski]

Overall to stop investing so much time into UI gimmicks and handle long standing bugs which should be solved months ago.

[Matthew Sinclair]

THIS!!!

[Anne Saunders]

Absolutely agree!

[Matthew Sinclair]

I'm sure its somewhere out there.

- Expansion of Operations Automaton Features (Formerly known as OpsGenie)

- Expansion of Jira/JSM Automation Features (like a targeted MS Teams/Slack command vs webhook or something generic/weird - may not be possible)

- Org Administrator controls - Good Lord - the list would go on and on and on.

Like this morning - looking at Rovo Credits consumed - search by user specifically without having to hunt and peck.

More user friendly version of Audit Log searches

Billing is still awkward/weird - specifically to do with User Counts.

A Sandbox to test Org Admin controls with - this would be big for me.

I could go on and on.

[Anne Saunders]

I've only logged 2 requests, but I've voted for many. Come to think of it, is the fact that we can celebrate the teenage birthdays of some JAC tickets a feature? 

(As of this morning, there are over 1,200 JRACLOUD work items that have been open for 10+ years)

[Shawn Stevens]

I'm not sure we have enough space here to really discuss this. As other have mentioned there are so many. I have discovered bugs, voted on a lot of features (that are actually bugs) that have been opened for a really long time as Anne mentioned. 

One of the big things for me lately is a lot of the new features seem more like Alpha's then Betas or hardened features. The features seem to address a very narrow use case. 

When they acquire a new technology, the integrations are not quite ready for prime time. Loom for example. I love the concept but when I looked at it is wasn't really integrated into the Atlassian Eco System and felt like a clunky process. It has gotten a lot better.

Quit reclassifying Bugs to Features, when the entire community thinks it is a bug. 

I agree with everything the others have mentioned so far.  

[Leslie Barrett]

I'd like to see an automated way to promote sandbox changes to production.

[Darryl Lee]

Here's a ... suggestion, I guess. Fix Sharepoint (and I guess all) Connectors?

What if Atlassian created a Teamwork Graph but nobody could see it? 

[Tomislav Tobijas]

I'd like for JAC to be migrated to the cloud 😅

If you've been to Team and at that 'feature request/suggestions' booth, you'd see that 'improve JAC' box almost always has the most marbles. But it's been quite a few years now, and it still looks like an interface from the 2010s 🫠 + the search there is horrific 

[Darryl Lee]

Well... Cloud Migrations are hard. :-D

But I think JAC Migration would be an amazing opportunity for Atlassian to demonstrate how to migrate a Jira instance that has tickets going back 2002:

https://jira.atlassian.com/browse/JRASERVER-1 

It would be fascinating to hear how they migrated integrations with Support systems to update custom fields like:

• Support Reference Count
• UIS (User Impact Score)

Do Votes and Watches get migrated? I have no idea. But you'd hope so!

(I referenced @Mirek's excellent What is JAC and how to use it? in the writing of this comment.)

[Anne Saunders]

@Darryl Lee can we designate that ticket as a Community Heritage Post?

[Darryl Lee]

@Anne Saunders  Yes, I feel like it needs a plaque. Maybe E Clampus Vitus could whip something up:

[Anne Saunders]

Exactly! Something appropriate and tastyeful. Maybe in blue. 😂

[Brita Moorus]

One suggestion I’d really love to see addressed is the ability to set Company Hub as the default Confluence landing page (again).

Company Hub is a great way to create a central entry point for employees, but it feels a little incomplete when users still can’t reliably land there by default.

For organizations using Confluence as an intranet or internal knowledge hub, being able to make Company Hub the true starting point would make the whole experience feel much more intentional and polished 💙

[Dave LIAO]

For those who don't know, I'm passionate about feature suggestion ID-240, which would be amazing to keep our user directories nice and tidy: https://jira.atlassian.com/browse/ID-240 - having a way to merge two Atlassian IDs.

However, https://jira.atlassian.com/browse/ID-6403 is more attractive to me: having the ability to associate multiple emails to a single Atlassian ID. Imagine how much cleaner our JSM queues would be, eh?

[Dave LIAO]

ID-240 is also my baby, I birthed it 11 years ago. 😂

[Matthew Sinclair]

Not sure how that would reconcile with a SCIM sitting there.

But def. a handy feature.

[Anne Saunders]

Congrats on your baby making it to a pilot program, @Dave LIAO !

[Dave LIAO]

@Anne Saunders - took forever, and it isn't really what folks asked for, but motion is motion? 😂

[Megan Kleinkort]

We have been trying to create a customizable template where a developer can select from a checklist of options what stories need created for an epic. Without lots of backend automation and integration of other systems, we've not been able to make it work :(