We have a large catalog of different physical parts, at last count the number of parts/materials we are trying to keep track of are in the millions. We are looking into creating an additional table in our parts database to try to keep track of each change to the millions of different parts. This would then go through another application to allow people to be able to look up any of these parts and all of the changes associated with it.
Our idea is to use JIRA in place of this new database table. By creating a JIRA task for each of the parts, we can give the task comments to keep track of minor details, as well as use statues for larger changes (having a status for discontinued, in development, etc). We are hoping to cut out the development time of what would otherwise be a complicated table, as well as leverage JIRA's ability to migrate and relate issues from one project to another. For example we could have a Help Desk/Customer Service issue tie into a change in the part database.
Right now we are asking on input regarding this before we start heavily developing it. Are there any potential road blocks? Has something similar to this been done before? Are there any 3rd party tools out there that would help this?
Thank you very much
--
Post by
dan_murphy@... - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38538_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user
