-
Suggestion
-
Resolution: Unresolved
-
None
We rely heavily on referencing Insight objects in our service desk while still trying to minimise the amount of custom fields and the current solution for creating Connections with the 10mb limit on results from the REST api is rarely an option since we often have to add searchable dropdown fields with many thousands of objects in the result set.
According to the documentation an integration with Insight has been "worked on" for a few years now, any actual progress there would be highly appreciated.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[FORMDC-27] Proper proforma/forms integration with Insight fields
any updates on this ? today is it's 3 years anniversary maybe it can get a feedback as a gift ? already exists in Cloud why not in DC ??
Yeah i need ask too. Why Data Center cant use Insight in ProForma Forms? really frustrates me
Our use case is (and I think we aren't the only ones):
- under certain circumstances a user needs to select a responsible person to approve or to make any decision
- in our use case this is going to happen as part of a form provided by ProForma due to conditional input
- thankfully we can pull Assets data such as employees via API to proForma however we cannot make further use of it
- an approver selected in ProForma is supposed to be added to "Approver" Jira field to grant permission for approval as part of the Jira workflow
- also this user needs to be emailed about the most recent approval request
How can we "sell" Jira Service Management as a nice tool to hundreds of colleagues if we need manual workarounds for such simple features?
We also need to train the users for additional tasks such as for those workarounds and we know, any manual effort of that kind may be a source of accidental errors done by human beings. Why not preventing this?
According to Atlassian support it is currently not possible to store Assets data pulled to and used in ProForma into any classic Jira field for any further use. If there's no (sustainable) way we'd appreciate to get this ability. Very soon. Please!
Any update when this highly requested feature is coming, or if it is even considered on the current product roadmap?
We as DC users have realized that our cries are being ignored. That's a fact! So in this case - we have directed our internal teams to work around these issues using solutions with what we have for the time being. smh! For this bug(out of many), we had to instruct customers to use the asset field on the top and guide them using UI/UX. Waiting to move to the cloud once FEDRAM is in place - Q1 2025?.
Please follow through with this. It's pretty regular heartburn for our users and our admins and the explanation for it not working is just silly.
Same here. I'd wish Atlassian wouldn't leave their DC customers in the dust. This ticket and adding attachments are the highest voted items and yet we see no response. Atlassian, customers remember poor treatment.
Don't want to shatter your optimism but first feature request tickets are "proper grown ups" nowadays.