Haddon Fisher Expert

Hi @Nicole Schwartz - that process can still be pretty time-intensive particularly when the project has a lot of request types...any chance there is some logic in the works to handle this more directly? This will ultimately be needed to convert team-managed projects to company-managed ones (which is absolutely a must…

Two clarifying questions around the new forms feature: The example above seems to be focused at team-managed projects. 1. Will this be available for company-managed projects? 2. If so, it seems like it could be possible to share a form with people who don't have permissions to actually create an issue, no?

My perspective is probably a bit jaded now but... * Don't expect anything from Atlassian. Their track record on getting things people actually ask for out the door is....uh...not so good. * Instead (and if you can afford it) look for add-ons. Most of these vendors are very responsive and within the bounds of the platform…

While working as an Atlassian consultant, I built a project for a client who wanted to use it as a "front end" for their code deployment system. Looking at the tool it was replacing and looking at the process they were trying to mirror, it must have been created in the early 90's - the resulting project had something like…

@Siobhan Flynn @Collista Lewingdon the crux of this in my mind is that creating projects around "ephemeral" things like work-projects results in a lot of Jira projects. This in turn has some not-so-great impacts: * From a technical perspective, Jira projects are pretty "hefty" - depending on how you set them up, they…

Can you provide the documentation around the new "CSV Import" functionality? A couple of things are jumping out at me: * The video above implies this functionality is part of the "project creation" wizard, which seems an odd choice. Can you only use this to import work into a new project? * The old CSV importer had a lot…

This feature feels like it solves the same problem dashboards are supposed to solve, but in a more restrictive and less useful way. Right off the top, most experienced Jira admins I know recommend against making Jira projects for specific initiatives or work-projects...but that seems to be a fundamental assumption for for…

1. "Overviews" feels like a less-useful replication of dashboard functionality, and I do not want to add even more overload to my users (and to my admins, who will need to answer all of the questions those users come up with). How can I disable this functionality for us? 2. I'd echo the ask to not add functionality to one…

I personally see the potential for admin-savings, but I haven't seen it pay out in practice, mostly because: * Administering Jira (even the small piece TMP gives you) still requires a lot of special knowledge. I find that my TMP admins are still asking me a lot of questions. * The superficial similarities between CMP and…

I may be just a country Jira admin with mud on my sneakers and hayseed in my headset, but embedding all of this in JWM projects feels like the wrong direction. All of these feel like less-good reproductions of things you already built, and in a less useful way. - The vast majority of my teams might be able to take…

Interesting - I'll take a look. Thanks!!!

Alex Hoogendoorn I agree with you that it's nice to have a "short name" for your epics. However I am in favor of this change because that nice-to-have is way offset by overhead of needing to add the field in places, explain the difference to users, etc.

Very ready for this, but more excited to see "Epic Link" get shown the door and have all parent-child relationships live in the same field. Would love an update on that timing!

This 100000%. Eat your own dog food!

I was definitely bit by one as a child Sergei Gridnevskii ;) I am surprised to hear your users don't bother you though. It seems like every day someone reaches out to me to ask how they can fix\adjust\do something only for me to find out "oh that very basic feature is not a thing in TMP's". 

* Disable team-managed projects. * If I get a basic question like "how can I export these tickets..." three times I write a doc on it in our Confluence's "Atlassian" space. * As much as possible "teach people to fish" instead of "giving out fish", particularly around Automation. You will be shocked how fast you end up…

Hey @Rohan Swami - is it going to be possible to retain the ability to link issues to parents via a field either in the central block or in the right-rail? The 'new breadcrumb experience' is not what we want.

Hey @Bree Davies , Thanks for the quick response! * I am ALWAYS down to chat, especially on this topic. Send me a calendarly or lemme know how I can reach out. * I'm glad to hear the features seem to all be small usability things, but I guess I'm frustrated that this is the stuff receiving attention. I'm not saying the UI…

I need to amend my answer a tiny bit - the other way I can think of to do this is the ScriptRunner feature "Behaviors". The just released it on Cloud, and while as of now I believe this is restricted to a handful of system fields, the Server version of this is much more robust and I have to believe they will expand it on…

This is (right now) not possible without an add-on like ProForma. FYI, ProForma was purchased by Atlassian and pieces of it are making it's way into core (forms is a good example) so it may be coming soon(ish) down the road. It is unfortunately no longer available in the Cloud marketplace though.

Do we know when this is going to be sandbox-capable? Seems like if you want people to play with things, we should be allowed to do that in a place where we play with things :)

Loving this level of detail and engagement! Couple of questions: 1. I'm excited to hear that y'all are re-focusing on UX and specifically consistency; its an area I think needs a lot of love. However it sounds like this is all happening within Jira Software - are there plans to address this between the various Jira…

Hi @Carol Low, 1. I must admit I find that very disappointing. Again, understand that you have a finite number of resources and an infinite amount of work and I absolutely do not want to be a Debbie Downer. And also, I am not seeing any real value in being able to "promote" a field. Maybe I'm the only one, but I'm having a…

Hi @Carol Low This is fantastic news! Couple of questions and thoughts: * We (and I suspect a lot others) now have a pretty big job ahead of consolidating all of these team managed fields and replacing them with instance-wide equivalents. This specific process (replacing a team managed project field with an equivalent…

Not really. Aside from Scrum boards (which make changes to the 'Sprint' field), Agile boards are mainly just "views" that sit on top of projects\issues, sort of similar to dashboards.

ACP-120 focuses on running Jira on Cloud in general, so it's going to be more of a foundation across the application. As @Rodney Dsouza _Atlassian Certified Expert_ said, ACP-420 is focused just on Jira Service Management. However I am not sure I would agree that: `Jira Admin for Cloud is almost like a subset of Jira Admin…

The "killer feature" of Cloud is that it's on Cloud, so you don't need to fight with Tomcat.

I don't have either Server or Gitlab to play with, but I see this doc which seems to be written by a human?

Hey @Jehan Gonsalkorale first, thanks for that long and detailed response! Atlassian's engagement with users has really undergone a sea change in the last year or so and I am HERE for it. I'm going to sign up for all of the early access I can and I'll send you feedback. However there is one question I would love an answer…

Hi @Jehan Gonsalkorale - I understand the inclination to make some improvements to the way configurations are built; the current model is complicated and takes some getting used to. However I think what I am hearing you say is "we absolutely don't want to make any big sweeping changes to how Jira works, we just want to…