Forum Discussion
BUG::PIPELINE::TEAMS ACTIVITY::SETTINGS NOT SAVED
- 2 years ago
So here is what happened now... I opened the pipeline again and upon clicking on each Teams activity and navigating to the settings, all the settings showed up as set yesterday.
Then I did this. I clicked on a Teams activity in the same pipeline that was copy/pasted from another pipeline (and that pipeline what copy/pasted from another workspace--I forgot to mention this yesterday). So, when I click on this Teams activity, none of the settings show up as they are in that other workspace pipeline. That's fine.
But then, if I click back on the Teams activity that was created within the pipeline I am currently working on, and whose settings just showed up as I had set them yesterday, now they show up as not set, like this:
So I think this is a client Javascript issue. Because like I said above, when I re-opened the pipeline today, the settings were all there as when I had set them yesterday. And now, after switching the focus back and forth between 2 Team activities (one natively created within the current pipeline, and one copy/pasted from another pipeline from another worskpace)) the settings appear gone again. I suspect after I save the pipeline, close it, and re-open it later, the settings will show as set properly again.
Hi Element115
Thanks for using Fabric Community.
As mentioned in the above steps, I created a repro. But I did not face any issue as you have mentioned.
The changes are still there.
Hence this is not a bug. Please try again and let me know if the issue persists.
Thanks
This is 100% a bug. I have reproduced the issue on my side and h ave been seeing this issue for 3 days now.