Votes
Answers
Views
Question
2
votes
1
answer
37
views
Using MF Connect version 4.3.1, it seems to be consuming alot of memory and connections with ALM octane.
3
votes
1
answer
50
views
We are using MF Connect 4.3.1 and we are synchronizing comments back and forth between AZDO and Octane. We have run into a weird issue where when we create a new comment in an azure ticket it is created as a new entity in Octane essentially making a duplicate issue in octane.
2
votes
1
answer
92
views
Tags:
MicroFocus Connect dropping connections and getting 401 errors
2
votes
1
answer
156
views
In MicroFocus Connect I am trying to create a "DataSource" for Jira but in the selection I do not see that I can select Jira as a possible datasource. Am I missing something.
2
votes
1
answer
187
views
So I am currently on ALM synchronizer and I want to migrate over to MF Connect soon. My concern is that we have alot of entities that are already mapped between the 2 tools and if we were to move to MF Connect we would get duplicates on all those issues since it would not be aware that some of them ...
2
votes
1
answer
37
views
Tags:
I recently started using MicroFocus connect, in ALM synchronizer we used to be able to run a "Full Sync" does MicroFocus connect have an equivilent for that?
2
votes
1
answer
35
views
I am currently using ALM synchronizer, does MicroFocus plan on continuing support for ALM synchronizer in the future. It seems like they are fixing less defects and enhancements?
0
votes
1
answer
131
views
asked 6 years ago by kaptainkayoss
updated 6 years ago by rich-text
I just upgraded to UFT 14.03 and the Autopass license server as well, which I believe is now version 10.3.0. Now, when I try to connect UFT to the Autopass license server, I am getting the error "License server unavailable". It was working fine before and I can ping the license server and po...
0
votes
1
answer
330
views
asked 6 years ago by godawgs
updated 6 years ago by David Hall
Hi, We have been experiencing issues connecting iOS device with Mobile Center. Tried first level troubleshooting and tried pulling up the device log using steps below: * Open command prompt and go to: \\libimobiledevice\\windows-amd64\\idevicesyslog.exe * Run below command: idevicesysl...