In RTIR_SiteConfig.pm I copied the original RTIR_Config.pm and edited to the
following:
Set(
blocks => {
initial => [ 'pending activation'],
active => [ 'active', 'pending removal' ],
....
}
_maps_ => {
....
incidents -> blocks => {
'open' => 'active',
'resolved' => [ 'active', 'removed' ],
'abandoned' => ['active', 'removed' ],
......
}
When I view System Configuration in the UI it looks as such:
_maps_ => {
....
incidents -> blocks => {
'open' => 'active',
'resolved' => 'array(0x25ecca8)',
'abandoned' => 'array(0x25ecc48)',
......
}
So again when I try to close an incident it closes all the blocks but I want to
be able to uncheck the blocks to keep them active but close the incident.
From the desk of Nicole A. Powell....
> On Dec 17, 2015, at 9:02 AM, Jim Brandt <jbra...@bestpractical.com> wrote:
>
>> On 12/17/15 8:50 AM, Nicole Powell wrote:
>> I made some changes to the mappings for blocks to incidents (allowing blocks
>> to remain active when incidents are closed) but the change is not working
>> correctly. Has anyone had this issue before?
> Editing the lifecycle could be a good solution to customizing for the
> workflow you want. Can you post what you changed (maybe the part of the
> lifecycle config)? When you say the change isn't working, can you provide
> more detail, like what you're seeing and how it's different from what you'd
> like?
>
> If you're not seeing any change at all, you can confirm the new lifecycle is
> being loaded by going to the System Configuration page: Admin -> Tools ->
> System Configuration.
>> From the desk of Nicole A. Powell....
>
