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

[PE-D][Tester A] Lacking a feature to add details about an asset #229

Closed
nus-pe-bot opened this issue Apr 5, 2024 · 1 comment · Fixed by #159
Closed

[PE-D][Tester A] Lacking a feature to add details about an asset #229

nus-pe-bot opened this issue Apr 5, 2024 · 1 comment · Fixed by #159
Assignees
Labels
bug.NotAllowedToFix response.NotInScope It is a valid issue but not something the team should be penalized for severity.High A flaw that affects most users and causes major problems for users type.FeatureFlaw Some functionality missing from a feature delivered in v1.4 in a way that the feature becomes less u type.PlannedEnhancements Features that are planned for future development
Milestone

Comments

@nus-pe-bot
Copy link

To be able to "Manages logistics and inventory in a professional capacity," as claimed as the purpose of the app, it would be important to capture the specific details of an item in the inventory. However, you can only add the name of an asset to a person, without any associated details.

This means you cannot track:

Specifications: Size, weight, capacity, model, power requirements – all these details inform storage, handling, and compatibility.
Conditions: New, used, refurbished, damaged – critical for valuation, deployment decisions, and maintenance.
Quantity: How many of a specific asset are available to meet demand?
Location: Which warehouse, vehicle, or area holds an asset. Essential for efficient retrieval and dispatch.
Associated Data: Maintenance records, usage logs, certifications, or rental agreements could all be tied to an asset.

Which is a significant compromise on its claim to be an inventory management tool for professional capacity.


Labels: type.DocumentationBug severity.VeryLow
original: Apzure/ped#9

@aureliony aureliony added type.Bug A bug severity.High A flaw that affects most users and causes major problems for users labels Apr 6, 2024
@aureliony
Copy link

aureliony commented Apr 6, 2024

A feature flaw that must be added to future enhancements.

@aureliony aureliony added the type.PlannedEnhancements Features that are planned for future development label Apr 6, 2024
@aureliony aureliony added this to the v1.4 milestone Apr 6, 2024
@aureliony aureliony added bug.MustFix A bug that must be fixed ASAP response.NotInScope It is a valid issue but not something the team should be penalized for type.FeatureFlaw Some functionality missing from a feature delivered in v1.4 in a way that the feature becomes less u and removed type.Bug A bug labels Apr 9, 2024
@aureliony aureliony added bug.NotAllowedToFix and removed bug.MustFix A bug that must be fixed ASAP labels Apr 12, 2024
@yisiox yisiox self-assigned this Apr 15, 2024
@aureliony aureliony linked a pull request Apr 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug.NotAllowedToFix response.NotInScope It is a valid issue but not something the team should be penalized for severity.High A flaw that affects most users and causes major problems for users type.FeatureFlaw Some functionality missing from a feature delivered in v1.4 in a way that the feature becomes less u type.PlannedEnhancements Features that are planned for future development
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants