Problem/Motivation

The Tugboat instance is creating the 2 Kanban tickets, but for some reason it is failing to make the 2 sprint tickets. It would be good to get this resolved to make QA easier.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork burndown-3612920

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

swirt created an issue. See original summary.

jeremylichtman’s picture

jeremylichtman commented

This worries me. Anything in watchdog?

jeremylichtman changed the visibility of the branch 3612920-tugboat-fix-sprint to hidden.

swirt’s picture

swirt
he/him
Primary language English
commented

No nothing in watchdog or the tugboat log. I don't think it's a big deal. I am sure it is just a mismatch between the drush commands in the tugboat yml that are creating the project and the one creating the tasks.

jeremylichtman’s picture

jeremylichtman commented

It might be the estimate sizes on those two tasks. The sprint project is set to use t-shirt sizes.

So:

vendor/bin/drush burndown:add_task --shortcode=SSPR --task_name="New Task on Sprint" --assignee=admin --reported_by=admin --priority=Medium --estimate=XS --description="This is a description of the task."
vendor/bin/drush burndown:add_task --shortcode=SSPR --task_name="An easy Sprint task" --assignee=admin --reported_by=admin --priority=High --estimate=M --description="A more urgent task."

I'm having issues pushing to drupalcode that I don't have the energy to dig into this evening. This should fix it though.

swirt’s picture

swirt
he/him
Primary language English
commented

Thanks. I figured it was likely something like that. I'll get it pushed up.

swirt opened merge request !56

  • swirt committed d8d7dd95 on 1.0.x 
    fix #3612920 tugboat sprint tasks not created.
swirt’s picture

swirt
he/him
Primary language English
commented
Status: Active » Fixed

Good eyes @jeremylichtman. That fixed it.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.