Skip to content

Conversation

@matejminar
Copy link
Member

  • Renaming option from Another version... to Another existing release.
  • Add usage tracking

image

Copy link
Member

@billyvg billyvg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM aside from existing

<MenuItemActionLink
{...actionLinkProps}
title={t('Another version')}
title={t('Another existing release')}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is existing needed? Seems a bit redundant. What is a non-existent release?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of customers and even some employees thought that they can enter there any version name (even future one) in which the issue will be resolved. (Especially in semver world)

{...deps}
onSelected={(statusDetails: ResolutionStatusDetails) =>
this.onCustomResolution(statusDetails)
this.handleAnotherExistingReleaseResolution(statusDetails)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for changing these :)

@matejminar matejminar merged commit 8ecc921 into master Jul 8, 2021
@matejminar matejminar deleted the feat/resolve-in-rename branch July 8, 2021 08:05
@github-actions github-actions bot locked and limited conversation to collaborators Jul 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants