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

Direct connectivity friends must have proxy user #2671

Conversation

danigargar
Copy link
Contributor

Added proxyUser field to Friends in Brand portal.

Type Of Change

  • Small bug fix
  • New feature or enhancement
  • Breaking change

Checklist:

  • Commits are named and have tag following commit rules
  • Commits are split per component (schema, web/admin, kamusers, agis, ..)
  • Changes have been tested locally
  • Fixes an existing issue (Fixes #XXXX)
  • Upport from existing Pull request #XXXX

Description

Additional information

@danigargar danigargar added +enhancement Enhancement schema Database changes tests Test core Core Libraries portal/brand Brand portal rest/brand labels Jun 3, 2024
@danigargar danigargar added this to the 4.1.0 milestone Jun 3, 2024
@danigargar danigargar self-assigned this Jun 3, 2024
@danigargar danigargar changed the base branch from bleeding to PROVIDER-1830-manage-friends-from-brand-portal June 3, 2024 16:31
@cruzccl cruzccl force-pushed the PROVIDER-1830-manage-friends-from-brand-portal branch from fe733cb to e2dad2d Compare June 4, 2024 15:49
@danigargar danigargar force-pushed the PROVIDER-1830-manage-friends-from-brand-portal branch 4 times, most recently from 7cc5d02 to 567bf1b Compare June 5, 2024 14:02
@cruzccl cruzccl force-pushed the PROVIDER-1830-manage-friends-from-brand-portal branch from 567bf1b to 2c6f650 Compare June 10, 2024 10:32
@danigargar danigargar force-pushed the PROVIDER-1830-manage-friends-from-brand-portal branch from 2c6f650 to e0253bb Compare June 10, 2024 12:06
Base automatically changed from PROVIDER-1830-manage-friends-from-brand-portal to bleeding June 10, 2024 13:48
@danigargar danigargar force-pushed the PROVIDER-1829-directConnectivity-friends-must-have-proxyUser branch 2 times, most recently from 3e4844f to f04b4e9 Compare June 10, 2024 14:53
Copy link
Contributor

@ironArt3mis ironArt3mis left a comment

Choose a reason for hiding this comment

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

Functional review required

@danigargar danigargar force-pushed the PROVIDER-1829-directConnectivity-friends-must-have-proxyUser branch from 4552439 to 957d4ea Compare June 10, 2024 15:10
@danigargar danigargar merged commit 6c76e8d into bleeding Jun 11, 2024
17 checks passed
@danigargar danigargar deleted the PROVIDER-1829-directConnectivity-friends-must-have-proxyUser branch June 11, 2024 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Core Libraries +enhancement Enhancement functional-review portal/brand Brand portal rest/brand schema Database changes tests Test
Development

Successfully merging this pull request may close these issues.

4 participants