Why does default JIRA workflow have 'Open' status instead of 'Opened'?

Is there any explanation to the awkward name 'Open' of the default jira workflow in version 5.1.x? All other statuses have proper names: 'Resolved', 'Closed', 'In Progress', 'Reopened'. And 'Open' falls out of the pattern. Is there any specific reason why this might have happened?

1 answer

1 accepted

3 votes

Open is a proper name. "Opened" would be "awkward" in both spoken and written English, because it's wrong. It just happens that Resolved, Closed and Re-opened are the words Atlassian have chosen to represent those three status in the workflow.

In fact, in-progress actually matches the pattern of "open" better than the other three - it's a description of a current state. You'd never say "in progressed" - that's completely mangled English (you'd say "started" if you wanted it to be consistent with the other three)

In English, you would say <object> is Open if it's open. We don't say "the door is opened" to describe it's current state, we say "the door is open". "Opened" is used to describe a past action, rather than a current state - "the door was opened" or even "the door was re-opened".

English grammar is fun... not.

Yeah, as a non-native English speaker, I say that English *looks simple* but when you're trying to express nuances it gets very easily damn *complicated*. But Open is a correct one, true.

It has a reputation of being a complex, nuanced and irrational language. As an Englishman, I can tell you that, well, um, it really deserves that reputation.

There's a lovely quote somewhere about English - it's something like "Many languages borrow from other languages, but English sometimes pursues them down dark alleyways to beat them unconscious and rifle their pockets"

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Wednesday in Jira

Join our webinar: How 1B+ feature flag events helped us build the new Jira

Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...

136 views 0 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you