Open snipe opened 7 years ago
I see that this is in the roadmap, but still adding a +1.
Just started using Snipe it and immediately ran into this issue. Apart from adding "custom" fields to e.g. Accessories, I also want to add already-existing fields to Accessories, for example: Status.
Why do some of these fields disappear for non-assets? Why not leave them in the list and allow user to choose whether to use it or not?
Just went to import licenses for Bluebeam and noticed my custom fields didn't show. That's when I found this article. Would very much enjoy this feature!
No one is talking about this one, but I really could use custom fields in users. Only 1 Phonenumber field?!? almost everyone has multiple number nowadays: office, mobile, soft (skype) phone, home... possibilties are endless, and most of the fields are available in AD for import, but no field to import them to.
+1 for custom fields in users and other non-assets.
Really hoping this will be done, we're currently stuck trying to add custom fields a license
+1
+1
+1
+1
+1
+1
+1 for this
+1 for this also
+1
Are we at all close to this?
In the Licence Plan is also missing, that some special Software only working with Dongle. But I can only enter the Software Licence. But this Software Licence can be variat to the Number of dongle for this Software. Please enter the possiblity that a Dongle and How many Dongle for a Software are available with the Software Licence. This where also a good choice, because some Software have Sharing Licences over Server with that Dongle entered.
still waiting for this feature.
+1
It's 2020 and we badly need this feature. I hope it will be implemented soon.
+1
+1
+1
+1
+1
+1
+1
+1
Also need this. The lack of customizing and ridiculous number of "Mandatory" fields is really turning me off to the whole product. Why have so many mandatory fields? Why not just let us choose?
+1 It is needed badly..Any ETA for this feature will be highly appreciated.
+99 -- this feature is BADLY needed to make this software much more robust and usable. My example is that I need to track UoM (units of measure) and a special internal product code for consumables. But this needs to be implemented system-wide, so that custom fields can be added to Licenses, Accessories, Consumables, Components, and People.
I'm sure it's complicated to implement, but possible, and would add at least 20% to the use-case scenarios where it could be implemented smoothly, vs. trying to kludge something together like trying to track consumables as assets so you can utilize custom fields.
+1
+1 .. urgently needed
Thanks for this great tool :-)
+1, I could absolutely use more custom fields in all the things.
+1
+1
+1
+1
+1 We are just now moving from excel to Snipe IT, having the ability to assign components to a asset and specify details such as in the instance of Ram, like dimm or so-dimm, ram size in GB, type like DDR4. This would also help with storage media tracking like hdds in which when the component is assigned to the machine you can add a unique asset tag. Now that does get into the issue of the difference between components and assets but I know many companies that track the individual components aswell as the usable machine, but the difference is the asset is assigned to a department or user while the components will only be assigned to asset itself and is of no use unless it is installed in the asset.
+1. We all really appreciate your work, just need some things to be more systematic before we can use it in production :)
+1 Having custom fields in /licenses would make my life much simpler as someone who uses the api almost exclusively for displaying asset data and approved software to people that don't have access to snipe-it within the organisation.
Thanks for your work!
+1 for custom fields to locations. Items I would look to track, using custom fields, for a location would include:
+1
https://www.youtube.com/watch?v=IrCEhRNgGHY
give me give me, i need i need i need
what about Bob
YouTubeBob Wiley begs for an impromptu psychiatric session from Dr. Leo Marvin while he's on vacation in New Hampshire.
It's coming, it's coming
+1 Need this
+1
It's coming, it's coming
thank you snipe! looking forward to this
Here is the link if you want to see the ticket https://github.com/snipe/snipe-it/issues/4261#issuecomment-700611362
Tina McCray Computer Technician Salem Academy and College 601 S. Church Street Winston-Salem, NC 27101 Fine Arts Center, Room 310
On Tue, Sep 29, 2020 at 6:22 AM ColorsASD notifications@github.com wrote:
+1
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/snipe/snipe-it/issues/4261#issuecomment-700611362, or unsubscribe https://github.com/notifications/unsubscribe-auth/APV2NPDNFOLLDARLPJCXMKDSIGYOFANCNFSM4D736C2A .
+1 Since Software Licenses are typically bound to software versions i wanted to add a custom field to licenses, which wouldn‘t work... Same for license type GPL, Commercial, personal with up to x devices and the like...
So any news on this one?
This has been proposed multiple times in various tickets, but I'm going to use this as a placeholder for that discussion moving forward, since the work behind extending custom fields beyond assets is basically the same, and would be a system-wide change.
I'll be closing all of the other related tickets and directing everyone here moving forward, as this issue will be easier to search on since it contains everything.