I am looking for advice regarding HEAT Development Projects and perhaps if anyone has used them, how you went about managing this.
This is currently my main concern as we haven't used projects before but given the current project I am tasked with, there have been a lot of changes to the non-production system so I emphasised we need to look into this feature further.
To provide some context, at the moment we are using an unorthodox setup, perhaps wrongly so, where we have Staging, UAT and Prod tenants. Our Staging site is essentially ignored, for lack of a better word, and all the work I am doing is performed on UAT. I have suggested testing this process by migrating the UAT setup onto Staging.
From what I can see, each transaction details is contained in a transaction set, which can then be assigned to a project. Should these sets be managed separately in some way? At the moment, there is an ever-growing list of transactions.
What things do not get transferred (have you noticed anything additional not explicitly detailed in any documentation)?
Did the procedure run smoothly - where there any 'quirks' that required attention post-migration?
Any advice/tips would be very much appreciated
EDIT: Thought I should add that we are a Cloud customer.
EDIT 2: In case anyone happens to be of the same mindset I was, I would recommend the following Ivanti Webinar: [Tech Brief On-Demand Webinar 2017] Cloud Service Manager Configuration Migration Process (formerly HEAT Software)