Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Priority description is wrong in CloudPublisher #3123

Closed
MMaiero opened this issue Oct 27, 2020 · 0 comments · Fixed by #3124
Closed

Priority description is wrong in CloudPublisher #3123

MMaiero opened this issue Oct 27, 2020 · 0 comments · Fixed by #3124
Assignees
Labels

Comments

@MMaiero
Copy link
Contributor

MMaiero commented Oct 27, 2020

Describe the bug
The description for the priority field is wrong in the CloudPublisher metatype in core.cloud.

To Reproduce
N/A

Expected behavior
N/A

Screenshots
N/A

Target Environment (please complete the following information):

  • Board [e.g. Raspberry Pi 3]
  • OS version: [e.g. provide the result of uname -a]
  • Additional info:

Additional context
Add any other context about the problem here.

@MMaiero MMaiero self-assigned this Oct 27, 2020
@MMaiero MMaiero added the bug label Oct 27, 2020
MMaiero added a commit that referenced this issue Oct 27, 2020
Added reference to Issue #3123 and #3107.
Removed the old reference to the PR related to #3107

Signed-off-by: Maiero <[email protected]>
MMaiero added a commit that referenced this issue Oct 27, 2020
* Fixed CloudPublisher description for the priority field.

Signed-off-by: Maiero <[email protected]>

* Updated version for the core.cloud bundle.

Signed-off-by: Maiero <[email protected]>

* Updated release notes

Added reference to Issue #3123 and #3107.
Removed the old reference to the PR related to #3107

Signed-off-by: Maiero <[email protected]>

* Missed a save in release notes

Signed-off-by: Maiero <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant