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

Team tags are not displayed correctly in Email Summary step #3508

Closed
pawelpabich opened this issue May 18, 2017 · 2 comments
Closed

Team tags are not displayed correctly in Email Summary step #3508

pawelpabich opened this issue May 18, 2017 · 2 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@pawelpabich
Copy link

pawelpabich commented May 18, 2017

When there are two teams where Id of one of them is a sub string of the other then then both are displayed in the summary. In attached example Teams-21 is selected but Teams-2 is a sub string of Team-21 so it will also be included. This only affect the way team names are displayed. During deployment the right teams are used.

Problems

  • getTags function takes a string, can we change it to an array of values?
  • there 8 copies of getTags function throughout the application, can we combine it into one and import as a module?

image

Started by (private): http://help.octopusdeploy.com/discussions/problems/54294

@pawelpabich pawelpabich added area/modelling kind/bug This issue represents a verified problem we are committed to solving labels May 18, 2017
@pawelpabich
Copy link
Author

pawelpabich commented May 26, 2017

Release Note: 'Send an Email' step summary shows now only teams selected by the user

@lock
Copy link

lock bot commented Nov 24, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

2 participants