Custom story workflow/states/status (was 'more acceptance states to support testing on multiple environments')

we are feeling frustrated by a lack of communication because tracker lacks a few states that are integral to our workflow. We need to be able to communicate when something has been accepted on our demo server, on staging and finally on production.

- not yet started
- started
- finished
- delivered
- accepted (on demo)
- rejected (on demo)
- accepted (on staging)
- rejected (on staging)
- accepted (on production)
- rejected (on production)
304 people like
this idea
+1
Reply
next » « previous
  • I’m frustrated
    This is pretty silly.

    I can't even have two rounds of QA "internally approved" and "client approved".

    Jumping through hoops and explaining to clients they have to add an "OK to push to prod" label is just not professional and has burned us many times already.

    Not having this is literally the worst part of the Pivotal Tracker experience for us.

    @Lisa Crispin, it's nice that labels are sufficient for your team, who I'm sure have a lot of experience with the software and feel comfortable using technology like this as part of a daily workflow. I'm telling you from a lot of personal experience that your average client finds this approach frustrating, confusing and prone to mistakes. When planning your roadmap please consider carefully who you think your customer base is, your hand-selected internal team, or agencies that have to regularly work with 3rd parties.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited

  • We also need this so that we can track stories as they pass through QA and customer acceptance. Out of frustration, some of our engineers are suggesting we move to Trello :0
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • 1
    Yes our organization absolutely needs the ability for custom "States" for example if we could just add the "Blocked" state that would be great - we are using labels as a workaround but its not really visible enough - it even be greater developer that when setting a Story to "Blocked" the Requester would get an email.
    • @Chris I agree, and also "On hold", per @NobodyHere (which means "we're partway through but a decision has been made to defer further work").

      However, like you say, this can be implemented using labels and smart search filters.

      @pixelperfect - how is the "Deploy" button different to "Deliver"? Unless you mean for it to actually trigger file copies, etc?

      Also, @pixelperfect - what is the difference between rejecting during demo or staging? And why cannot a label be used? As for rejection on production - wouldn't this count as a new bug in a delivered feature?

      @Lisa - I can appreciate this might be a difficult one to make a call on. If you open things up to allow any number of steps then the system has the potential to become unwieldy which can lead to poorer reputation. However for those who know what they're doing, a little more flexibility might be perfect. All the best deciding how to resolve it! However, one change that might be helpful is the suggestion by @Rutabaga to allow customisation of button text. I say this only because in one context I use PT for something completely different than software development, and being able to emphasise a different, business-appropriate metaphor would add a level of intuity to the system. That said, I've been using it this way for about 4 years - the learning curve to equate one state in the system with one state in our business was basically zero and the system is intended to be for software development anyway, so perhaps even this suggestion doesn't warrant much merit.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • A related issue is to track when a story is in state "Started" but blocked by a pull request. I developed a little app (free to use!) which :

    - Add a label pull-request to the story when a pull request is created
    - Add a note to the story when the Pull Request is updated (someone pushes on the branch)
    - Mark the story as "Finished" when the Pull Request is merged, removing the label.

    The code : https://github.com/ssaunier/mergehook
    The app you can use right away ! https://mergehook.herokuapp.com/
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • I’m suggesting you dig around for a feedback link in the app
    I don't think anybody is reading this that has any influence on the design of pivotal tracker (anymore).
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • It would be nice to be able to define any variety of custom states. Taiga.io does this well. You can define each state and exactly what it means. We have been wanting this for a while to add a "Code Review" state (among others) before it moves on to accept.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated

next » « previous