Cannot link defects to test cases in test-case-mgmt mf-24 getting permissions error

ALM Micro Focus ALM / Quality Center
, , , , , , ,
1

Our test team cannot link defects to test cases in test-case-mgmt module. When testers try to add defect links from test case details view, they get a permissions error even though they have tester role assigned.

The error appears when clicking the “Link Defect” button from a test case. We’ve checked project permissions and workflow transitions - testers have read/write access to both test cases and defects. Field security settings look correct too, but the link action consistently fails.

This is breaking our traceability completely. We can’t track which test cases found which defects, making root cause analysis and regression testing impossible. Has anyone seen permission issues with defect-to-test-case linking in mf-24?

2

After reviewing similar cases in mf-24 deployments, this permissions error during defect-to-test-case linking involves multiple security layers that must all align correctly.

Project Permissions: The tester role needs more than just read/write access to test cases and defects. Entity linking is a separate permission scope in ALM. Go to Project Customization > Project Users > Roles and verify the tester role includes:

  • Test: Modify Test (standard)
  • Defect: Modify Defect (standard)
  • Cross-Module: Create Entity Links (often missing)

The third permission is critical and not included in default tester role templates. Without it, users can edit test cases and defects individually but cannot create relationships between entities.

Workflow Transitions: Defect workflows in test-case-mgmt can block linking based on defect status. The link operation is treated as a defect modification, so if your defect is in a status that restricts modifications, the link fails.

Review your defect workflow configuration. Common blocking scenarios:

  • Defects in “Closed” status with no allowed transitions
  • Defects in “Fixed” status restricted to developer role only
  • Workflow rules that prevent modifications after certain time periods

The solution is to either:

  1. Allow relationship modifications in all workflow states (recommended)
  2. Create a separate workflow transition for “Add Link” that’s permitted in restricted states
  3. Update the workflow to allow testers to modify defects in any status when the change is only adding a relationship

Field Security: Mf-24 introduced granular field-level security for relationship fields. Even with correct module permissions, the specific relationship field between test cases and defects might be restricted.

Navigate to Project Customization > Entities > Test > Fields and locate the “Defect Links” field (field name varies by project). Check the field security settings:

  • View: All project members (should include tester role)
  • Modify: Often restricted to test-lead or admin roles by default

Update the “Modify” permission to include the tester role. This field-level security is separate from entity-level permissions and frequently causes linking failures.

Library Access: If your test-case-mgmt uses shared test libraries, permissions become more complex. Test cases in libraries have their own permission structure independent of the project where defects exist.

Verify library permissions:

  1. Go to Libraries > [Your Test Library] > Security Settings
  2. Check if testers have “Contributor” or “Editor” role in the library
  3. Ensure library permissions allow creating links to external entities (defects in project repository)

Cross-repository linking requires write access in both the library (for test cases) and the project (for defects). A tester with project access but library read-only permissions will encounter the error you’re seeing.

Verification Steps:

  1. Test with an admin account to confirm linking works (isolates permission vs. configuration issues)
  2. Review ALM audit logs to see the exact permission check that’s failing
  3. Verify test cases are not in locked or checked-out state
  4. Confirm defects are in a workflow status that permits modifications
  5. Check if cross-module linking is enabled in project settings

Resolution: The most common cause in mf-24 is missing “Create Entity Links” permission in the tester role combined with field-level security restrictions on the relationship field. Update both:

  1. Add cross-module linking permission to tester role
  2. Grant tester role modify access to defect relationship fields on test cases
  3. If using libraries, ensure testers have contributor access
  4. Review defect workflow to allow relationship modifications in all states

After addressing these four security layers - project permissions, workflow transitions, field security, and library access - testers should be able to link defects to test cases successfully. The key is understanding that entity linking in ALM requires explicit permissions beyond standard CRUD operations on individual entities.

3

Workflow transitions can block linking even when base permissions are correct. If your defect workflow has a state where defects are locked from modifications, the link operation fails because ALM treats adding a relationship as a defect modification.

Review your defect workflow in test-case-mgmt. Look for workflow states with restricted transitions that might prevent relationship changes during certain defect statuses.

4

The tester role might have test case and defect access, but linking entities requires a separate permission called “Manage Links” or “Create Relationships”. This permission is often missing from default tester role configurations.

Check your project roles and verify the tester role includes entity linking permissions, not just CRUD access to individual modules.