nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira 7 - Core/Software/JSD

J. Caldwell

I'm going to get it out of the way and say "I haven't tried it yet in a test environment..." because I'm reading docs and I'm unclear on some things.

So...is JIRA Software (formerly Agile) still a plugin? Is "JIRA Core" basically just the old vanilla JIRA Server?

We run multiple JIRA instances for BU specific customers. Sometimes folks just want vanilla JIRA and then later on, a dev team in their area moves from one instance to another, so then we need to add JIRA Software/Agile to that instance. Before we would just buy the plugin and slap it in and away we go. Are we talking about a difference now in how that happens where we need to have to re-deploy the app instead of just iteratively adding to it? I am unclear based on the documentation how it all works. JSD seems straightforward still as it is just a plugin.

Accepted answers

Nic Brough -Adaptavist-

>So...is JIRA Software (formerly Agile) still a plugin? Is "JIRA Core" basically just the old vanilla JIRA Server?

Well, no. But yes. Sort of.

JIRA Core is pretty much JIRA Server without any add-ons. JIRA Agile and Service Desk are now "applications" rather than add-ons. They are more tightly integrated into the core than other add-ons (although you won't really notice that apart from the way users are handled, and the licencing stuff). The distrubutables of "Software" and "Service Desk" are JIRA Core with the relevant application pre-installed, but there's no real difference between downloading JIRA Core and then going "oh, let's enable Software/SD as an application", waiting for them to install and licencing them.

All comments

Nic Brough -Adaptavist-

>So...is JIRA Software (formerly Agile) still a plugin? Is "JIRA Core" basically just the old vanilla JIRA Server?

Well, no. But yes. Sort of.

J. Caldwell

So...are we talking about something more like Fisheye/Crucible, where adding a license turns functionality on/off? Here's what happens and why I'm really concerned about this change. A BU starts using Jira Core. 6 months down the line, there dev team moves into that instance and wants Agile. Do I now have to re-deploy the application using the "jira software" package? What happens in 3 months if they add JSD? I have to re-deploy the whole application again? What happens if they decide to step down to just "core"? I have to redeploy again? That's a lot of time spent in test and if something goes wrong, it isn't just a "disable the plugin" or "pull it back", its a "roll the whole damned app back." Likewise, if I want to add a bit that comes with a more recent version of Agile, I'm not upgrading a plugin...I'm upgrading the whole app, which again, not efficent use of my time. As always Nic....thanks for taking the time.

Nic Brough -Adaptavist-

It's the bit about "let's enable X as an application" that matters here. It's not the same as add-ons, but it's similar. If you suddenly want to stop using the Software functions, remove the user's access to it. (I think you can turn them off too, but I've not tried)

J. Caldwell

Yeah...I'm going to have to play around with my home instance over the weekend to see. I've also cut a ticket to Atlassian for clarification.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-service-desk

jira-software

jira-administration

jira-core