@TanyaGorbunova i still see no clear evidence as to a fix for this issue. Surely, instructing someone to ingore this issue and create a new issue is masking how long teams have been struggling with the integration between Ready API and SCMs?
We are still working around the issue via a manual process.
There are several reasons why I asked to submit a new topic. Here are only some of them:
There are several issues discussed here. So, it's unclear which exact issue @ArthurM faced.
Our Support Team doesn't monitor the discussions on a regular basis. It's a community - we believe that most of the questions can be resolved by talking with peers. If we see that the question is quite complex and require the investigation, we can invite a Support Team to the discussion.
It's always to better submit one issue per discussion. In this case, the conversation will go only around one topic and it will be extremely helpful.
@frankkilcommins, have you contacted the Support Team regarding any issues posted here? I'm sure the Support team along with the R&D team always do their best to make sure that our customers are satisfied with ReadyAPI.
--------- Tanya Yatskovskaya SmartBear Community and Education Manager
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
I didn't not create a new project, I've implemented a workaround to avoid conflicts on changed property values, and actually haven't used ReadyAPI activlely since, so, not sure if other types of conflicts are still actual.