Journal Entries reference field

[snowie-swe]

NetBox version

v3.1.6

Feature type

Change to existing functionality

Proposed functionality

Would like to see Journal entries extended to include a "reference" field.

Use case

If there is an issue on a VM / Devices that involves a hardware replacement / software hotfix or similar.
It would be very nice to be able to search for a case number / ticket from the vendor "reference"

Same can be used for reference to internal tickets / issues

Database changes

dont know

External dependencies

dont know

[jeremystretch]

It would be very nice to be able to search for a case number / ticket from the vendor "reference"

Is this something we should build into core, or would it be more appropriate as a custom field on the JournalEntry model? I'm just considering validation possibilities, but maybe I'm over-thinking it.

[snowie-swe]

It would be very nice to be able to search for a case number / ticket from the vendor "reference"

Is this something we should build into core, or would it be more appropriate as a custom field on the JournalEntry model? I'm just considering validation possibilities, but maybe I'm over-thinking it.

In general i believe that extending custom field to more/all modules is a good middle ground.
It allows organizations to add smaller things without requiring additional development from the community.

[mmfreitas]

Is this something we should build into core, or would it be more appropriate as a custom field on the JournalEntry model? I'm just considering validation possibilities, but maybe I'm over-thinking it.

A custom field, custom link and tags could be useful in the JournalEntry model.

I don't think this is what you meant but if journaling were to be built into the core, I would propose having the ability to journal on "create"/"update"/"delete" of anything, and the possibility to journal from the changelog of said event. Keeping this history even if changelog is deleted

[martinum4]

Had a similar issue right now, kinda wished we had custom links and fields for journals too.
This has a huge potential addon value for end users, e.g. one could easily build links to external issue trackers or third parties.

Proposal for Issue Opener: Change Title to "Extend Data model of Custom Links and Fields to include journal entries"

[jeremystretch]

A custom field, custom link and tags could be useful in the JournalEntry model.

Agreed. I've opened #9006 to propose this and plan to implement these changes in v3.2.

I'm going to close out this issue as I believe the original use case is best served via the creation of a custom field for the JournalEntry model.