Dear,
we are using Jira and Confluence for our production of goods by using heavily the workflow and automation engine from Jira.
We are searching now for a solution or best practice how to implement a quality-control process for goods in Jira.
While testing a software release is like running multiple different test-cases with one (new) build or version, testing goods is like running the same test-case multiple times for one "deployment".
E.g. you receive an article X from your supplier, 10.000 pcs. You want now perform a quality control by testing 100 pcs out of those 10.000 pcs. You have to perform the same test 100 times for the same delivery.
This is the moment when software-QA tools fail.
Any suggestions?
Some self talk while seeking input :)
We setup a QA Project in Jira for a high valuable, low frequency article.
The underlying process is simple, just like new, check-ok, check-fail.
All QA metrics were defined as custom fields and added to the mask.
The fix-version field reflects the date of delivery.
Each issue represents an article / material.
300 incomming articles = 300 new tickets.
While using Jira mobile app on a tablet, QA is able to take pictures if required for further clarification.
Now, we can track and evaluate the quality of our supplies.
With the add-on app "time in status" we're able to visualize the progress of quality over time.
Jira real-time dashboards are used during management calls and issue details are used for further clarification with engineers.
This is a huge improvement to manage the quality with our suppliers.
Next step will be a solution for high-volume articles.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.