Snipe-it: Different tag auto-increment fields for different locations.
It would be nice to have an opportunity to use different auto-incremented tags for different locations. For example, if you choose first location while adding new asset, snipe takes last inserted tag for this location and increments it. If you choose second location - it takes last tag for second location.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
miffril
All 48 comments
I would also like this.
We have various locations across the world, we want the asset tag to pre-pend, let's say the location where the asset originates, when entering the system.
MrJingles46
on 11 Sep 2017
đź‘Ť
I'm on the same boat here. So please consider this feature. It would also be cool of one could set different prefixes for every location. So that one would get uk-00001 for the location UK and us-00001 for the location US.
Thank you :)
faxesystem
on 27 Oct 2017
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!
![stale[bot] picture](https://avatars3.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 20 Jan 2018
I'd also like to see this extend to individual companies when multi company support is enabled.
For example, Company A would get an asset prefix of BAZ0001, while Company B would get an asset prefix of ITASSET0001.
carlashley
on 30 Jan 2018
I was just getting ready to ask if this was an option, this would save me tons of time and headache. Having it based on default location or even Category (Desktop + DSK#####, Laptops = LPT#####, etc).
AZPacketPlumber
on 17 Apr 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!
stale[bot]
on 16 Jun 2018
Bad stale bot.
faxesystem
on 16 Jun 2018
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 15 Aug 2018
Yes my staley stale bot I would still like this feature. :)
faxesystem
on 15 Aug 2018
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 15 Aug 2018
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 14 Oct 2018
Yes.
faxesystem
on 14 Oct 2018
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 14 Oct 2018
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 13 Dec 2018
Would still like to have this feature
faxesystem
on 13 Dec 2018
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 13 Dec 2018
I would very much like to see this for categories as a static part of the asset tag included at time of asset creation., such as MIC-001, where the MIC is the prefix for a category and the 001 is incremented for each new item in that category. The prefix should be static as assigned during creation so that if I change the category later, I don't want it to change the asset tag prefix unless I specifically tell it to since printed labels would become inconsistent and could no longer be used for lookup.
During asset creation, it could autofill the asset tag like it does now, but then change once a different category is chosen, but we could type in something else if we want just the same as it is now.
niteowl099
on 22 Jan 2019
I like the idea of having a different prefix based on the company
mwolfe1
on 6 Feb 2019
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 7 Apr 2019
Still relevant
On Sun, Apr 7, 2019 at 11:45 AM stale[bot] notifications@github.com wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/3914#issuecomment-480601794,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AtKeFGAn9Ivis84LN_01mK1A3P8tb0zSks5vehKQgaJpZM4PJ8gG
.>
Michael Wolfe
mwolfe1
on 7 Apr 2019
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 7 Apr 2019
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 6 Jun 2019
Would still like to have this feature
mwolfe1
on 6 Jun 2019
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 6 Jun 2019
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 5 Aug 2019
Still relevantÂ
Michael Wolfe
On Mon, Aug 05, 2019 at 1:17 PM "stale[bot]" < ">"stale[bot]" > wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (
https://github.com/snipe/snipe-it/issues/3914?email_source=notifications&email_token=ALJJ4FEUCUEBJPNLDP5QOQ3QDBOCTA5CNFSM4DZHZADKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3SPI2Q#issuecomment-518321258
) , or mute the thread (
https://github.com/notifications/unsubscribe-auth/ALJJ4FEVBRERVRFXHHUDYRTQDBOCTANCNFSM4DZHZADA
).
mwolfe1
on 5 Aug 2019
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 5 Aug 2019
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 4 Oct 2019
Still relevant
On Fri, Oct 4, 2019 at 1:52 PM stale[bot] notifications@github.com wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/3914?email_source=notifications&email_token=ALJJ4FEXEIH72VGCPPA7LVDQM57HXA5CNFSM4DZHZADKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAMNKFY#issuecomment-538498327,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALJJ4FHJDUQRPVR2SHBUPT3QM57HXANCNFSM4DZHZADA
.>
Michael Wolfe
mwolfe1
on 4 Oct 2019
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 4 Oct 2019
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 3 Dec 2019
Still relevantÂ
Michael Wolfe
On Tue, Dec 03, 2019 at 3:58 PM "stale[bot]" < ">"stale[bot]" > wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (
https://github.com/snipe/snipe-it/issues/3914?email_source=notifications&email_token=ALJJ4FGGUKRB3IKGYQ6WCJ3QW3CARA5CNFSM4DZHZADKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF2ZLNI#issuecomment-561354165
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/ALJJ4FDW4QW2UCQWMPQNPKTQW3CARANCNFSM4DZHZADA
).
mwolfe1
on 3 Dec 2019
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 3 Dec 2019
And it's still relevant for me.
alter
on 13 Dec 2019
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 11 Feb 2020
Still relevantÂ
Michael Wolfe
On Tue, Feb 11, 2020 at 7:53 AM "stale[bot]" < ">"stale[bot]" > wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (
https://github.com/snipe/snipe-it/issues/3914?email_source=notifications&email_token=ALJJ4FD3DQNPCTTTDANSMFLRCKNV7A5CNFSM4DZHZADKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELMJTOA#issuecomment-584620472
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/ALJJ4FHHFQYKDFTY67YJ4HTRCKNV7ANCNFSM4DZHZADA
).
mwolfe1
on 11 Feb 2020
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 11 Feb 2020
Is there any progress on this feature request?
harryangel2608
on 16 Mar 2020
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 15 May 2020
Yes
On Fri, May 15, 2020, 7:32 PM stale[bot] notifications@github.com wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/3914#issuecomment-629253604,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLGR2XBMFS3SQWKEKAK453RRVDQXANCNFSM4DZHZADA
.
harryangel2608
on 15 May 2020
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 15 May 2020
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 18 Jul 2020
Yes
Michael Wolfe
On Sat, Jul 18, 2020 at 1:58 AM "stale[bot]" < ">"stale[bot]" > wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (
https://github.com/snipe/snipe-it/issues/3914#issuecomment-660432890 ) , or
unsubscribe (
https://github.com/notifications/unsubscribe-auth/ALJJ4FGMMZIGQBEA54LCWYTR4E2WRANCNFSM4DZHZADA
).
mwolfe1
on 18 Jul 2020
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 18 Jul 2020
Yes
On Fri, May 15, 2020, 7:32 PM stale[bot] notifications@github.com wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/3914#issuecomment-629253604,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLGR2XBMFS3SQWKEKAK453RRVDQXANCNFSM4DZHZADA
.
harryangel2608
on 18 Jul 2020
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
on 20 Sep 2020
Yes
On Sun, Sep 20, 2020, 9:19 AM stale[bot] notifications@github.com wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/3914#issuecomment-695644236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLGR2QAFKYY7DQZ25U3C3DSGV3VRANCNFSM4DZHZADA
.
harryangel2608
on 20 Sep 2020
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
stale[bot]
on 20 Sep 2020
Related issues
comisso
·
4Comments
alextheberge
·
4Comments
Rungea96
·
4Comments
bricelabelle
·
3Comments
sopheaouk
·
3Comments
Most helpful comment
I'd also like to see this extend to individual companies when multi company support is enabled.
For example, Company A would get an asset prefix of
BAZ0001, while Company B would get an asset prefix ofITASSET0001.