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

bug: Tasks in a Proposed Changes related to another one #5002

Closed
BeArchiTek opened this issue Nov 20, 2024 · 2 comments
Closed

bug: Tasks in a Proposed Changes related to another one #5002

BeArchiTek opened this issue Nov 20, 2024 · 2 comments
Assignees
Labels
group/backend Issue related to the backend (API Server, Git Agent) priority/2 This issue stalls work on the project or its dependents, it's a blocker for a release type/bug Something isn't working as expected

Comments

@BeArchiTek
Copy link
Contributor

Component

Frontend UI, API Server / GraphQL, Not Sure

Infrahub version

1.0.5 and 1.0.6

Current Behavior

If I create 2 Proposed Changes one after the other from 2 differents branches, without merging them, the Tasks in the 2nd Proposed Change have the first one as related node
image

The data diff is showing the proper changes so I wonder if it's only "visual"

Expected Behavior

The Tasks are correctly linked to the current proposed change

Steps to Reproduce

  • Load the demo-schema
  • Create a branch test( UI or CLI infrahubctl branch create test)
  • Create a new attribute to a node (i.e ddescription2 to InfraInterface)
  • Create a proposed change from the branch test to main
  • Create a branch test2( UI or CLI infrahubctl branch create test2)
  • Create a new attribute to a node (i.e dname2 to InfraInterface)
  • Create a proposed change from the branch test2 to main
  • Check the tasks

Additional Information

No response

@BeArchiTek BeArchiTek added the type/bug Something isn't working as expected label Nov 20, 2024
@dgarros dgarros added group/backend Issue related to the backend (API Server, Git Agent) state/need-triage This issue needs to be triaged labels Nov 25, 2024
@dgarros dgarros added this to the Infrahub - 1.1 milestone Nov 25, 2024
@exalate-issue-sync exalate-issue-sync bot removed this from the Infrahub - 1.1 milestone Nov 25, 2024
@exalate-issue-sync exalate-issue-sync bot added state/need-triage This issue needs to be triaged and removed state/need-triage This issue needs to be triaged labels Nov 25, 2024
@exalate-issue-sync exalate-issue-sync bot added this to the Infrahub - 1.1 milestone Nov 26, 2024
@exalate-issue-sync exalate-issue-sync bot added the priority/2 This issue stalls work on the project or its dependents, it's a blocker for a release label Nov 26, 2024
@exalate-issue-sync exalate-issue-sync bot changed the title bug: Taks in a Proposed Changes related to another one bug: Tasks in a Proposed Changes related to another one Nov 26, 2024
Copy link

[From lykinsbd]

Validate that this is still an issue in 1.1, as the underlying task behavior has changed.

@BeArchiTek
Copy link
Contributor Author

Still present in 1.1.0b2
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
group/backend Issue related to the backend (API Server, Git Agent) priority/2 This issue stalls work on the project or its dependents, it's a blocker for a release type/bug Something isn't working as expected
Projects
None yet
Development

No branches or pull requests

3 participants