-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different tag auto-increment fields for different locations. #3914
Comments
I would also like this. |
👍 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 :) |
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! |
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 |
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). |
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! |
Bad stale bot. |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Yes my staley stale bot I would still like this feature. :) |
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! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Yes. |
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! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Would still like to have this feature |
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! |
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! |
And it's still relevant for me. |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
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 (
#3914?email_source=notifications&email_token=ALJJ4FD3DQNPCTTTDANSMFLRCKNV7A5CNFSM4DZHZADKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELMJTOA#issuecomment-584620472
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/ALJJ4FHHFQYKDFTY67YJ4HTRCKNV7ANCNFSM4DZHZADA
).
|
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! |
Is there any progress on this feature request? |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Yes
…On Fri, May 15, 2020, 7:32 PM 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
<#3914 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFLGR2XBMFS3SQWKEKAK453RRVDQXANCNFSM4DZHZADA>
.
|
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! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
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 (
#3914 (comment) ) , or
unsubscribe (
https://github.com/notifications/unsubscribe-auth/ALJJ4FGMMZIGQBEA54LCWYTR4E2WRANCNFSM4DZHZADA
).
|
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! |
Yes
…On Fri, May 15, 2020, 7:32 PM 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
<#3914 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFLGR2XBMFS3SQWKEKAK453RRVDQXANCNFSM4DZHZADA>
.
|
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Yes
…On Sun, Sep 20, 2020, 9:19 AM 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
<#3914 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFLGR2QAFKYY7DQZ25U3C3DSGV3VRANCNFSM4DZHZADA>
.
|
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! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Still relevant
Michael Wolfe
…On Fri, Dec 25, 2020 at 11:23 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 (
#3914 (comment) ) , or
unsubscribe (
https://github.com/notifications/unsubscribe-auth/ALJJ4FCH7HYP5DDDWIHVQQ3SWS4ALANCNFSM4DZHZADA
).
|
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! |
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.
The text was updated successfully, but these errors were encountered: