New Feature: Comment for dynamic fields

[hkais]

On systems with lots of dynamic fields, is a lack of having the need to add a description to the dynamic field.
Especially to have the option to define the comment field as mandatory.

Please imagine a company organisation in EU.

If you consider the EU wide average tenure of only 3-6y at the same employer and assuming only one admin, you will face the following situation.
A system of 10y age will already have 2-3 different minds (persons) working on the dynamic fields.
And consider how often you face organisations with a mandatory requirement about requiring to document elementary settings. How often this is really done well? In my experience less than 5% of the orgs doing it well.
Now consider the typical case there 2-3 admins are working on the administration, how the dynamic fields are getting created and named.

So IMHO, where shall be a mandatory comment field per dynamic field, which is requiring to document the usage of the specifically created dyn field.

this is related to viewtopic.php?p=178998#p178998

Do you see a chance to add this field to the database dynamic_field table and to add it to the UI?
I think it would improve the "documentation" state of a important feature in znuny.

[zzz]

Having a multi-line comment field (like ACLs) is a thing worth discussing.

But I am strongly against a mandatory comment field. That would not only violate the expected user experience in the admin area, it would also be annoying.

The app can't fix the lack of willingness to document processes within an organization.

[hkais]

But I am strongly against a mandatory comment field. That would not only violate the expected user experience in the admin area, it would also be annoying.

I confirm that the mandatory feature shall NOT be hard coded. It shall be configurable.
Default: as is, means non mandatory
BUT, Admin shall be able to decide if he wants to make the comment here as mandatory for everyone who creates new custom fields. This will be IMHO the common thing in bigger orgs, to enforce a rule "document features" and a dynamic field is nearly always implementing new features.

So both requirements, your's as not mandatory by default, and the IMHO common way which the organisation can decide will be having the option to set the comment as mandatory. This setting can be added as many other mandatory settings in the system settings itself

[root]

Hi,

Please use https://github.com/znuny/znuny-feature-requests/ for feature requests. We do not follow feature request in the forum.

- Roy

[hkais]

Hi,

Please use https://github.com/znuny/znuny-feature-requests/ for feature requests. We do not follow feature request in the forum.

- Roy

It is worthless work to post a feature request if it will not be implemented and issue will be closed.
Therefore the discussion here.

If more users find this feature helpful, I will post a new feature in github soon.
And also refer to this discussion.

So it would be helpful here to get a brief:
- feature sounds very good, we may implement soon, plz post on github
or
- feature is good, but on our low prio, plz post on github
or
- we do not consider it helpful, so I can save our and your time, without posting it in github.

Hope you can understand my approach?
Can you give a brief feedback on this feature request?

[root]

HI,

Sorry to disappoint you, but we have a clear workflow. I you want to suggest a feature please use the mentioned repository and follow the issue template.

- Roy

[Yeti]

HI,

Sorry to disappoint you, but we have a clear workflow. I you want to suggest a feature please use the mentioned repository and follow the issue template.

- Roy

Hi Roy,

maybe i'm getting something mixed up here, you could clarify the workflow?
The link you posted 'https://github.com/znuny/znuny-feature-requests/' saiys, that the requested feature should be discussed in the forum first.

Screenshot 2024-07-20 181221.png

Isn't this exactly what we do here?

To the topic at hand: i think this is a good idea. We have customers with huge systems where the possibility to set as description mandatory would prevent some confusion.

[root]

maybe i'm getting something mixed up here, you could clarify the workflow?
The link you posted 'https://github.com/znuny/znuny-feature-requests/' saiys, that the requested feature should be discussed in the forum first.
Screenshot 2024-07-20 181221.png
Isn't this exactly what we do here?

Hi,

You're right, mixed that up. Probably because most feature requests were just done by creating a new issue in the repository. I will take this as a question back to clarify this for the future.


Regarding the feature idea: I personally do not like too much documented inside the system, because I'm a huge fan of a proper documentation that includes everything related the business/use cases implemented in Znuny. And this is not possible inside the application, especially not just with multi-line comments. I prefer clear naming schemes.
Besides my personal preferences, I see this as good idea for small systems. The only issue I have with make it mandatory, even with a system configuration.

- Roy

[root]

maybe i'm getting something mixed up here, you could clarify the workflow?
The link you posted 'https://github.com/znuny/znuny-feature-requests/' saiys, that the requested feature should be discussed in the forum first.
Screenshot 2024-07-20 181221.png
Isn't this exactly what we do here?

Hi,

You're right, mixed that up. Probably because most feature requests were just done by creating a new issue in the repository. I will take this as a question back to clarify this for the future.


Regarding the feature idea: I personally do not like too much documentation inside the system, because I'm a huge fan of a proper documentation that includes everything related the business/use cases implemented in Znuny. And this is not possible inside the application, especially not just with multi-line comments. I prefer clear naming schemes for dynamic fields.
Besides my personal preferences, I see this as good idea for some systems. The only issue I have with make it mandatory, even with a system configuration.

- Roy