Hi @Abc
These changes aren't recorded right now; but there is a feature request you could vote for - check out: JSDCLOUD-11728
Ste
Hi @Abc , indeed there is no versioning built in. You could check the audit logs but I don't think anything is recorded. My advise is two fold, first restrict who can make changes and second use Confluence to record any changes. In the end version control is left to the user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Abc -
Just to confirm you are referring to the FORM configuration associated to your JSM issues (not the actual request type configuration?
If yes, then FORMs associated with each project are not shared with other projects. Only project Administrators have the right to configure/change the FORMs design. If you access the Forms section from Project settings of a project, you will see when the form configuration was updated. Currently, there is no audit tracking/versioning built-in to the form setup. This is why project admins need to communicate with each others to ensure all changes are done are agreed upon for the project and properly documented for record keeping.
On the other hand, if you are referring on FORM's update after the issue is created and where the form is associated with it, then you should look into on each form's settings tab to determine on who can update the associated FORM.
Here is a reference link on Form's settings - https://support.atlassian.com/jira-service-management-cloud/docs/about-form-settings/
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.