Inventory/asset/stock management: creating a "Librarian-type" workflow? Stock movements and similar. Edited

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?





0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,720 views 17 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you