8000 [FEATURE REQUEST] Improve Attachment Handling When Replenishing Supplies and Copying to Services · Issue #990 · hargata/lubelog · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
[FEATURE REQUEST] Improve Attachment Handling When Replenishing Supplies and Copying to Services #990
Open
@Solverz-0

Description

@Solverz-0

Checklist
Please make sure you have performed the following steps before submitting a new feature request, change [ ] to [x] to mark it as done

Description

Currently, when using the "Copy Attachments" option while adding a supply to a service/repair/upgrade, all attachments ever associated with that supply are copied over, regardless of when the attachments were added.


Reproduction Steps:

  1. Add a supply item and attach a file (e.g., receipt_v1.pdf).
  2. Use that supply in a service/repair/upgrade with Copy Attachments enabled → Attachment is correctly copied.
  3. Replenish the same supply (same name, same ID), and add a new attachment (e.g., receipt_v2.pdf).
  4. Use the same supply again in a new service/repair/upgrade with Copy Attachments → Both receipt_v1.pdf and receipt_v2.pdf are copied over.

Desired Behavior:

Only the attachment(s) relevant to the currently used supply quantity should be copied, not all historical attachments for the supply.


Suggested Solution:

Associate attachments with the supply quantity at the time of attachment. That way:

  • When a supply is replenished and a new attachment is added, that attachment is only associated with the new quantity.
  • Future services using that supply will only copy the attachments relevant to the portion of stock being used.

This avoids the need to create a completely new supply entry with a different name just to avoid attachment carryover, which IMHO is an error-prone workaround.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0