Hello all,
I am currently trying to set up a Service Desk Portal and we are trying to have "Background fields" like "Requestor Name", "Requestor Department", "Request Date etc."
These fields should not be visible when a person is raising an issue via the portal, but, obviously, to us.
Also they should be automatically filled by the programm. So, for example when User A from Department A raises a request on the 10.10.2020 the fields should be autofilled accordingly. The users will be only within our organisation and the Service Desk is hosted within our Intranet, if that matters.
Is this possible to do?
Also I only have project admin rights, I am no Jira admin so sorry if the answer is rather obvious- might be I just can't access the required functions.
Hey @Blake ,
You can automate the auto-filling of fields by using Elements Connect to create dependencies between fields. Elements Connect is an application that brings your external data into Jira's custom fields.
If I understand your use case correctly, you can use an LDAP database as a datasource and configure Elements Connect to display the information you need: "Applicant Name", "Applicant Department", "Application Date", etc.
In fact, you can find an LDAP use case in the free demo portal and more information about configuring an LDAP database in our documentation.
If you want to implement your use case using Elements Connect, I can invite you to try our application and contact our support if you have difficulties with the configuration. You can also book a 1:1 call with me to recreate your use case if needed.
Let me know if this addresses your issue.
Armand.
Hi @Armand Luziau_Elements_ Armand, thank you very much for your exhaustive answer! Also Kudos to you @Alex Koxaras _Relational_ , you two have helped me greatly!
However, this part of the project was pushed back now, so I'll probably come back in a few weeks when its again on the top of the agenda.
Again, much thanks to both of you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Blake if either me or @Armand Luziau_Elements_ (or both) provided a suitable answer to your question, kindly accept any answer as correct. This will help new people on the community to find proper answers. Thanx!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alex Koxaras _Relational_as I could not yet get to trying the solutions out due to the postponement of the project, I cannot yet judge which answer works out well in the end. I will have to come back anyway and take another look at the answers as soon as the project is under construction again- then I will also highlight the most helpful answer :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Blake and welcome to the community!
Yea you can do that, either from the request types with hidden fields which can take a predefault value, or within the issue types workflow by using post functions. The latter can be done only by a jira admin.
Request types, if you are the project administrator, can be edited by you, as long as these fields have already created by a jira admin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.