As far as I see, all existing inventory/asset mgmt plugins and tutorials are based upon "one asset == one issue" rule - presuming the assets are unique.
What if they are NOT unique, but still need to be tracked? Say I have, um, a library of printed books, with several identical copies of each, and there's actually no point in cloning them into individual issues?
So, that would be something like having an "item card", the total amount of such items accounted, and the related assignments/states. That would allow knowing "we have N copies of that particular book, of which M are on-shelf, and X are handed out; the ones handed out are assigned to user1 (holds 1 copy), user2 (holds 2 copies), userX (holds X copies)".
And all the typical stock management stuff, like creating new books, writing off ones damaged/lost/not returned, requesting more copies to be acquired etc.
Any ideas if that's feasible with JIRA?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs