Join example in docs is incorrect

Bug #1761827 reported by Brad P. Crochet
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mistral
Fix Released
Medium
Brad P. Crochet

Bug Description

The workflow in the join: 2 example is incorrect. And the description of it is confusing.

Brad P. Crochet (brad-9)
Changed in mistral:
assignee: nobody → Brad P. Crochet (brad-9)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to mistral (master)

Fix proposed to branch: master
Review: https://review.openstack.org/559392

Changed in mistral:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to mistral (master)

Reviewed: https://review.openstack.org/559392
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=7657458e61503dd2b2cbe85090d635ca66d35600
Submitter: Zuul
Branch: master

commit 7657458e61503dd2b2cbe85090d635ca66d35600
Author: Brad P. Crochet <email address hidden>
Date: Fri Apr 6 14:13:48 2018 -0400

    Fix join examples and text

    The 'join' example for using a number did not have a proper workflow.
    It looks like it was copied from the 'all' example and not completely
    changed. Also, disambiguate the wording of the description for that
    example. It used the word 'once' in a place where it looked as though
    it meant 'one time' instead of 'as soon as'.

    Change-Id: I9b89768c0f0b7d325db08ea9345965a9263a64c8
    Closes-Bug: #1761827

Changed in mistral:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/mistral 7.0.0.0b1

This issue was fixed in the openstack/mistral 7.0.0.0b1 development milestone.

Dougal Matthews (d0ugal)
Changed in mistral:
milestone: none → rocky-1
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.