4 ms·

> I wish the comments were more specific about which features they don’t like. I have a very specific complaint: the ease which all sorts of custom fields can

> I wish the comments were more specific about which features they don’t like. I have a very specific complaint: the ease which all sorts of custom fields can be added for _everyone_. Sales will want to add a field to hold their contract status. Lo and behold, engineering now has it. It can be done in the proper way, but it seems that doing it at a global level is easier since that's how multiple Jira installations at multiple companies were configured. All I want is a ticket, with a title, description, assignee, the current status, an easy way to transition, and comments. That's it. Let my project _opt out_ of any global customization if making global stuff is unavoidable. Also, the newest Jira UX is... terrible. Tickets should not be THAT easy to edit. How often do we want to change a ticket's description, or title? I'd say, not often. If we do, there's really no harm in having an "edit" button. Old Jira versions had one.

Buttons840 4y ago
I had a similar thought: Jira is very customizable; if people hate something that is so customizable then part of what they're hating is the organizations customization of it. I've seen the same thing at multiple companies. Someone comes up with a Jira workflow, it doesn't match the needs of some people, but the company wants to standardize on that workflow, so now people are stuck using a stupid workflow that doesn't work for them. I've also seen a bunch of stupid custom fields on every single ticket. Is this Jira's fault or the organization's fault? You complain but the word from your immediate manager is that the team is already in hot water so escalating complaints about the Jira configuration isn't going to help, etc.
- lmm 4y ago
  If only one organisation did that, it would be that organisation's fault. When every organisation using Jira does that, it's Jira's fault. Why does everyone standardize on a company-wide workflow that the developers can't change with a bunch of stupid mandatory fields? Because that's what Jira nudges you to do. Workflow editing is for managers only, fields are mandatory by default...
lp0_on_fire 4y ago
> Tickets should not be THAT easy to edit. How often do we want to change a ticket's description, or title? I'd say, not often. If we do, there's really no harm in having an "edit" button. It's very useful for when the user submits a ticket with "My computer isn't working" as the title and "excel is broken" as the description.
- exyi 4y ago
  I'd not mind to press edit to change it.
rozap 4y ago
Every time I'm highlighting and ctrl+c'ing something out of a ticket and it turns into edit mode, I tense up a little bit. Ugh.

Buttons840 4y ago

I had a similar thought: Jira is very customizable; if people hate something that is so customizable then part of what they're hating is the organizations customization of it. I've seen the same thing at multiple companies. Someone comes up with a Jira workflow, it doesn't match the needs of some people, but the company wants to standardize on that workflow, so now people are stuck using a stupid workflow that doesn't work for them. I've also seen a bunch of stupid custom fields on every single ticket. Is this Jira's fault or the organization's fault? You complain but the word from your immediate manager is that the team is already in hot water so escalating complaints about the Jira configuration isn't going to help, etc.

lmm 4y ago
If only one organisation did that, it would be that organisation's fault. When every organisation using Jira does that, it's Jira's fault. Why does everyone standardize on a company-wide workflow that the developers can't change with a bunch of stupid mandatory fields? Because that's what Jira nudges you to do. Workflow editing is for managers only, fields are mandatory by default...

lp0_on_fire 4y ago

> Tickets should not be THAT easy to edit. How often do we want to change a ticket's description, or title? I'd say, not often. If we do, there's really no harm in having an "edit" button. It's very useful for when the user submits a ticket with "My computer isn't working" as the title and "excel is broken" as the description.

exyi 4y ago
I'd not mind to press edit to change it.

rozap 4y ago

Every time I'm highlighting and ctrl+c'ing something out of a ticket and it turns into edit mode, I tense up a little bit. Ugh.