Only if your installation is set up that way. Here's how I create a Jira ticket in my organisation: 1. Click "Create Issue", 2. type in a summary (the headline), 3. type in the detail, 3. Click "Create"
If you have more stuff to fill out, that's an issue with your local configuration. Blame your Jira master, not Jira or Atlassian :D
You only have to enter two fields in your workflow and it feels clunky? This doesn't jive with my experience at all but perhaps you're on an old version or it's resource starved. Once you start beating up jira or confluence you have to start tweaking defaults and jvm settings to get the most out of it.
I assume managed account means it's hosted by someone else. Unless it's Atlassian themselves they're probably being cheap and giving it as little resources as possible and it not being on-prem probably contributes to the feeling of slowness.
Jeez so many replies to jira hate with. Oh buts how you configure it. Oh its this. It's that. Stop apologising for a shitty product. If a user find it hard. It's failed. End of story.
There is no universal solution. Every product will have users who find it hard to use. Speaking out about the fact that you find it manageable is valuable information and may show that there are more users who find it easy to use than not.
I agree. Things for some people, they don't work for others. But you cannot blame users and say "oh its how you configured it" "its good out of the box" etc.
If its failed for 1 user, its a shit product.
If its a success for 1 user, it's a great product.
It's GOOD for a user to say they find it easy and why.
It's GOOD for a user to say they find it hard and why.
1 helps the user give a product a second chance by learning of his pitfalls.
1 helps the company improve their product to make it easier for more users.
My point is that apologists shouldn't come in here and blame users for a shitty product.
Let's say -ferinstance- you have kick-ass, seriously best-at-what-it-does software that's only localized in Japanese, and a uniglot USian attempts to use it. They're gonna have a hard time. The software will very likely fail them, because they will be unable to understand anything they're being told by the software.
Does that make the software shit? No. No, it does not. The software is great, it "just" needs to be localized in order to be great for a wider swath of humanity.
Can you please elaborate on this configuration? What is the general nature of the configuration changes you're making? Or, how is your workflow affecting the product. I ask as I am in an organization right on the cusp of implementing JIRA, and I would love to steer the implementation team toward a more useful configuration than the clunky defaults, with which I've had prior experience.
* Setting up several statuses (more than in the default) to reflect backlog, selected, in progress, testing, deployed
* Creating an appropriate board which splits everything into columns by status and rows by user
* Setting up a few quick filters to find things like anything which has been in the backlog for more than 6 weeks or bugs which haven't seen activity in the last 48 hours
* Integrating GitHub. Being able to kick a ticket over to QA from your commit message is awesome.
Beyond that, I mostly focus on stripping out default things to make the workflow simpler. I don't need my software to enforce that I can't move a ticket to deployed straight from in progress, and stripping out those extra rules makes it easier to deal with.
Issue trackers are like utilities, like electricity and water. If they're doing their job, they're invisible. You only notice them when they're broken.
As a result, all issue trackers have more detractors than promotors, with the vast majority of users being neutral.
That said, I've used RT (holy shit no), Pivotal Tracker (drinks too heavily from the dynamic DOM/JS koolaid, sucking up all RAM and CPU in the known universe), and JIRA. I'd take JIRA over the others.
I've used Mantis and Bugzilla and I'd also take JIRA over those.
JIRA is the best bug tracking software I've used since I left Microsoft, which was over a decade ago. Sometimes I still miss Raid, particularly it's ability to build complex queries, but also the ability to connect to any team's project. At the time, it was supposedly the only internal tool used throughout the entire company.
If you have more stuff to fill out, that's an issue with your local configuration. Blame your Jira master, not Jira or Atlassian :D