Learn More
Resend Email
6
ctnqhk
3y

This is why you shouldn’t try to redefine words and deviate from accepted word definitions.

Dev team/product decides to put the word [content] in a JIRA ticket’s title. To dev, this means “it’s a CMS change and no code push required.”

A new marketing team comes on board along with a few “website manager” type folks. They start putting [content] in JIRA ticket titles, but they think [content] means content change and their requests do require a code push instead of a CMS update.

First time it happens, I comment on the ticket and tag the reporter. I explain what [content] actually means for us. Most importantly, I explain that it tells us how to prioritize the request and how to deploy the changes.

Happens again. And sometimes they’re requesting changes for the next day when we only do weekly releases. I suspect they didn’t believe me because I’m lower in the chain. It’s also easy to forget because we are using “content” to mean something different here. I ask my boss does [content] still mean what I think it does? It does. 😕

I just decide to comment on the ticket and let them know the request requires a deploy and that’s why I’m changing the title of the ticket. They might also have to wait until the weekly release.

Overall, a bunch of lunacy all around.

devrant

rant

why
Favorite
Ranter
Comments
  • 4
    3y
    A workflow is only a workflow if all parties involved agree on it.

    That's the root problem of any media shared by several different teams / group of people.
  • 4
    3y
    Despite all the stress this caused. You should try to be content that you did your best.
  • 2
    3y
    Given that, in the *english dictionary*, "literally" is defined to mean "figuratively", I'm gonna have to say you're full of shit if you think your use of language is the only correct way.

    English is defined descriptively, ie how it is used is considered valid because that's how people use it.

    The French have a language institute that trys to tell everyone what's correct. Should tell you everything you need to know.

    Only really came to object to that.
  • 1
    3y
    @atheist this is why English is just full of shit 🙃 who’s way is right amiright
  • 0
    3y
    I don’t think anyone was wrong. I just want things to be done consistently.
  • 1
    3y
    Off the cuff doesn't seem like a ludicrous thing for them to assume "Hey maybe this team wants all CMS changes to be prefixed this way" - but you were correct to tell them they were wrong.
    If your hints don't stick you might need to send a prefix manual to the other team.
  • 1
    3y
    @jiraTicket The best part of this is [content] was my boss’s idea. He’s actually c-suite. So I’m just going to tell him his idea isn’t being easily adopted by the new folks. Let’s see how they respond to a c-level exec.
  • 0
    3y
    @ctnqhk I would avoid doing that.

    If I was part of the other team I would just go "I dunno what levels has to do with anything. he can be whatever level - doesn't help people intuitively understand what Content means"

    Migjt boil down to "if you want this prefix to indicate CMS-ONLY...maybe you should just call it that"
  • 1
    3y
    Reading the rent makes me wonder if your team even have a document explaining what ticket type to use for X or Y targeting people who'll be filling up your backlog.

    And regarding English vs French (coming from a bilingual in both languages), at least French doesn't have the problem of people misusing words to make up new definitions or to have different meanings.
  • 0
    3y
    @Berkmann18 I have a feeling they did receive some training on JIRA. They definitely know some basic rules, like if you change ticket details when a dev is working on it then you talk with the dev first. But they ignore it.
  • 1
    3y
    @ctnqhk Oh dear! They need a reminder or refresher then.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment