Greg D Rising Star

@April Chi have you all thought about a way to allow additional members to be added into a Managed Team by non-admins that is connected to a Group? We have some Groups that are SCIM syncing and others that are just in Jira and both of those may need to be a Team and also may need to have non-admins edit them (maybe SCIM…

Thanks again for offering this "ask-me-anything", Brett! Sorry that I jumped into a lot of design elements and feedback (those are so top of mind right now based on what our stakeholders are relaying). Maybe I missed the window, but piggybacking off of Morgan, let me try to ask other questions that may be more up your…

I responded to another place, but also realized visuals could help here too... If we cannot be given control, Atlassian can first fix JSM, change every section to stars only to start, hide all sections on the left under "More" except Starred, Projects (workspaces), and Filters. Then it might be less confusing. Maybe…

@A A Ron Geister _Trundl_ are you referring to the new nav at home.atlassian.com? I do think that is much better under the new nav. But Jira is where most of the feedback is targeting. I wish us admins could control everything about it and set a starting view for everyone that makes more sense and is less overwhelming. If…

I ended up writing a ton about this again, so figured I should nest it as a reply. In Orgs that have been in Cloud a long time, there are a ton of starred items and other sections that will never be needed on the left-hand panel. So the first reaction of every user that gets switched into the new view is "This is so much…

As mentioned here, would be really helpful if site admins can define the starting point for what is hidden and shown for users when they are switched over.

I had a similar thought here. I had recommended sea foam green out of preference, but what I was mainly suggesting is that some colors are not readable nor aligned across elements right now.

Was searching to see if there had been any updates to the control of the right-panel on the "Your work" page. Unfortunately, even in the new navigation, and even for people that have never used Opsgenie, it seems we are stuck with that panel stealing the real estate for the advertisements. Stephen, you may have already…

Hey @Josh Sherwood, I also asked this here on your other post, but are you all also addressing "project" along this journey of change? * That has always been the weirder term since a "project" would have an end (and most Jira projects never end). Atlas uses the term project and that has been folded into Atlassian…

FYI, Atlassian is evolving their Goal-tracking right now into Platform Experiences: Atlas is Evolving Within that evolution is Goal Types that are now specifically defined as Objective and Key Result (with more goal types coming). Might help with the structure you are looking for with your sub-goals. What is a Goal? -…

Looks like there is a feature request for this here: ATLAS-141 - Allow users to bulk create/update goals 

As others mentioned, hoping we get a simple privacy toggle that exists both at creation and after creation on all "Projects" (confusing name as mentioned here) and Goals (currently no way to restrict individual goals and can only do that for projects at creation). Need to be able to lock visibility to owner/contributors at…

Also hoping we get a simple privacy toggle that exists both at creation and after creation on all "Projects" (confusing name as mentioned here) and Goals (currently no way to make individual goals private and can only do that for a project at creation). Need to be able to lock visibility to owner/contributors at all…

Hoping we get a simple privacy toggle that exists both at creation and after creation on all "Projects" (confusing name as mentioned here) and Goals (currently no way to do at all). Need to be able to lock visibility to owner/contributors at all stages... found this request: ATLAS-65 - As a user, I'd like to create private…

@Josh Sherwood checking in... some good questions here in the comments. Any chance some of us can sync up with you to chat somehow?

@Ted Hewitt agreed, we have always wanted it fully configurable where we can control by instance, project, issue type (work), workflow transition, and user on whether they should be writing internal or public at any given moment. For every setting in Jira, it seems to make sense to have an Atlassian starting point as a…

I was thinking that once the new transition screen came, the commenting would match the full issue view with a collapsed bar: Similar to what James mentioned, that is, in a way, showing both at once... also saves real estate and allows focus to be on other field values you may be capturing across different transitions. If…

Hey @Josh Sherwood, are you all also addressing "project" along this journey of change? * That has always been a weird term since a "project" would have an end (and most Jira projects never end). Atlas uses the term project and that is getting folded into Atlassian Home/Platform Experiences, so now there are two concepts…

FYI, this bug was created for this back in October: JRACLOUD-84891 - URL field type opens the link in the same browser tab instead of opening in a new tab. There is some other related behavior I was investigating and saw this community post.

Hey @Eric , are you still working on this? I would love to chat with you (and just seeing your Calendly link). Any dates around the JQL filtering being available? Would be extremely helpful for us.

@Joshua Buison maybe it doesn't hit all of your use-cases, but just as an fyi, one other thing that is useful about the automatic grouping by domain is that it can share the requests in the customer portal for that entire Org of that domain and then you can let those external people see each other's requests without…

I was trying to write during Team '24 but my comment didn't save. Hoping this is still considered during the week and I can get a tree planted... I would say: * Wherever they're needed Thanks!

@Dan W I saw your comment here after JSDCLOUD-9463, but just to echo what I wrote there, internal being the default is much less risky in case an agent is writing internal details, sensitive info, mentioning internal people, or confusing directions that will not make sense externally. But would definitely love to have more…

@Gabriel Raubenheimer are you closer to consolidating the Reporter, Request Participants, reference to who raised via, and Organizations fields with the new "customer details" section? It would be really helpful if all of that was only in a single place when the feature is turned on. Either: * Get rid of new Customer…

Are we getting closer to the Reporter and Request Participants fields both living within the new customer context glance and not being duplicated in other places on the issue view? If we use this feature, we need it to all live in just that one place and be the actual editable fields to reduce cognitive load. Within the…

@Amirbehzad Eslami can you also remove the ability to at-mention the Reporter and Request Participants in JSM projects? These users are falling outside of your new intended logic. We cannot take away the Browse Project permission from the Service Project Customer - Portal Access or it breaks the project and so we cannot…

I responded in our email convo, but I probably should have highlighted it here for everyone. Unfortunately, right now it will not make sense to store this in the customer/organization section because the values are not always equal to each other in our use-cases and so it will be confusing for the agents (a Reporter could…

Hello again. So looks like there is a new "Customer" grouping starting to flow into the issue detail view. This is really confusing as it will only describe the Reporter (Request Participants are customers too, yet they are not in that grouping). This section is hogging real estate, and it is duplicating fields since we…

Hi @Gabriel Raubenheimer, I just sent you an email with this, but I thought it might be good to add here too. One thing that would be really helpful with the new feature is hiding the "Organizations" section on the left panel for users that do not have permissions to manage organizations. If this site setting is toggled…

So looks like in JSM projects via Project settings > Features > Customer service management the awesome new feature of being able to store additional details on a customer has been added! This is huge. Will agents soon be able to edit the true portal-only customer's display name in the Customer details section of a…