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

I can see which flow nodes are not mapped in instance migration mode #18571

Closed
1 task done
pedesen opened this issue May 16, 2024 · 1 comment · Fixed by #18683
Closed
1 task done

I can see which flow nodes are not mapped in instance migration mode #18571

pedesen opened this issue May 16, 2024 · 1 comment · Fixed by #18683
Assignees
Labels
component/frontend Related to a frontend component component/operate Related to the Operate component/team kind/feature Categorizes an issue or PR as a feature, i.e. new behavior version:8.6.0-alpha2 Marks an issue as being completely or in parts released in 8.6.0-alpha2

Comments

@pedesen
Copy link
Contributor

pedesen commented May 16, 2024

Description

This adds tags to indicate which of the source flow nodes are not yet mapped in instance migration mode. This improves visibility and helps users to see which source flow nodes they still need to map.

User Story

Scenario: As an Operate user
    Given I am in instance migration mode (mapping step)
    Then I can see a tag next to each unmapped source flow node in the bottom table
    When users select a target flow node
    Then then the related tag disappears

Designs

https://www.figma.com/design/tnqak7ht4Hb4VCGygvLNFU/Version-Migration-HFW?node-id=1970%3A161543&t=EpWVp0Rz3Aw2Hajq-1

Acceptance Criteria

  • A tag is shown next to each unmapped source flow node in the bottom table
  • The tag disappears when the user has selected a target flow node

Definition of Ready - Checklist

  • The issue has a meaningful title, description, and testable acceptance criteria
  • If documentation needs to be updated, an issue is created in the camunda-docs repo, and the issue is added to our Operate project board.
  • If HELM charts need to be updated, an issue is created in the camunda-platform-heml repo, and the issue is added to our Operate project board.
  • Potential Security risks have been considered and added to the product-hub issue risk assessment
  • Cross-team dependencies have been considered

Optional:

  • Design input has been collected by the assignee

👉 Handover Dev to QA

  • Handy resources:
    BPMN/DMN models, plugins, scripts, REST API endpoints + example payload, etc :
  • Example projects:
  • Versions to validate:

Docker file : in case that it needed to be tested via docker share the version contain the fixed along with version of other services .

  • Release version ( in which version this fixed/feature will be released)

📗 Link to the test case

Tasks

@pedesen pedesen added kind/feature Categorizes an issue or PR as a feature, i.e. new behavior component/operate Related to the Operate component/team component/frontend Related to a frontend component labels May 16, 2024
@pedesen pedesen self-assigned this May 16, 2024
github-merge-queue bot pushed a commit that referenced this issue May 27, 2024
## Description

- Add tag to each source flow node row which is not mapped to a target
flow node

## Related issues

closes #18571
@Szik
Copy link

Szik commented May 28, 2024

Acceptance Criteria have been tested successfully.

@korthout korthout added the version:8.6.0-alpha2 Marks an issue as being completely or in parts released in 8.6.0-alpha2 label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/frontend Related to a frontend component component/operate Related to the Operate component/team kind/feature Categorizes an issue or PR as a feature, i.e. new behavior version:8.6.0-alpha2 Marks an issue as being completely or in parts released in 8.6.0-alpha2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants