cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Integrity Source: Share members via drag&drop

Integrity Source: Share members via drag&drop

We are using many shared members that have to be added one after another to a new project via Member/Add from Archive.

It would be helpful to be able to use drag&drop to share members from one sandbox to another.

11 Comments
Aquamarine

Since the requested Drag&Drop is -afaik- connected to the functionality MoveMember, the realisation of such a new functionality should be be done without affecting this one.

Also this requested function should be possible to be used as well in the Sandbox views as well as in the Project Views.

Aquamarine

IMHO a Copy&Paste Action would be preferable to Drap&Drop.

It would also be nice if the pasted member could be easily set to a "dynamic share", meaning the member rule to sync the revisions between the two shares.

Yes, the given functionality with the "ClientLink.js" Trigger works, but Setting these links up can be a p.i.t.a.

Alexandrite

There exists already an RFC 439722 for this idea.

Gravel

Thanks for submitting this idea. However, PTC do not have any plans to work on this enhancement - based on future product roadmap for Integrity Lifecycle Manager.

Aquamarine

RfC's (esp. older ones) as well as SPR's will be commented like following:

"Not part of Integrity's functionalities.

If you like to have such a function, please refer to Ideas ..."

Happened more than once to older cases of mine ...

Without any relating entry in the case itself.

Aquamarine

Could you please provide more details, like part of roadmap which makes this idea not relevant for implementation?

I would like to understand, why this idea won't be implemented.

Aquamarine

can this decision be read as a "fade-out" strategy for Source, meaning that it will be maintained but not further enhanced?

Gravel

PTC is going to focus on the UI Replacement Project & this is our current roadmap. The area that you are mentioning is really UX in my opinion and specifically for Source. As you may be aware we have a UI Replacement Work Group that is operating currently and we would have a similar group when we get to Source UI Replacement - once that gets formed we will seek your inputs for Ideas like these, but there is no plan to implement this in the current GUI. We can still mark it For Future Consideration but we will not be looking at implementing this in the current UI

 

 

Gravel

I won't say that ! As mentioned above, we're not considering to implement this source related idea in current GUI format. When we get to new Source GUI - we shall be able to take up relevant ideas then.

Aquamarine

Siddharth Somani schrieb:

(..) We can still mark it For Future Consideration (..)
 

 

Sounds good. Right now idea is still marked as "No Plans to implement"

Gravel

Changed to "For Future Considerations" !