Use a custom instead issue's priority

[likehopper]

Today, the definition of an « SLA term » is based on the « SLA type » and the Issue priorities enumeration ( present by in an issue natively ). Issue priority cannot be filtered by project and all statuses are always displayed.

[likehopper]

I identify three solutions at the moment:

• keep issue priority, the native enumeration field
• use a custom field which can be selected by SLA
• use a specific field of the plugin integrated in the issue

[zdenarik]

@likehopper Good work. It looks like good. Can I understand right that item sla_get_date is datetime field that shows deadline of SLA? Or that is field that shows datetime when SLA was created?
And one more question - how did you mean exactly things in note Required ? Shall I send this information to out Redmine admin and he will undestand?
Thank you

[likehopper]

The item sla_get_date is datetime field shows when SLA actually started.

I'll see if it's possible to display a forecast end date, but it's difficult to determine. Because, if the status changes, and SLA goes back to "pause", the date becomes in an unknown state.

Yes, you can send the “required” note information to your administrator. In this note, I explain that it's necessary to rebuild two tables (sla_caches & sla_cache_spents), all the functions & all the views of the module.

[zdenarik]

OK, thank you. I see.
And what about forecast end date - when status changes to Waiting for Answer, forecast and date stay unchanged, Resolving time will stop and when it changes to In Progress for example, then it will add remaining time from Resolving time to forecast end date and updates it... is that possible?

[likehopper]

When the status changes to « Waiting for response », it is no longer possible to determine the « forecast end date ». It'll only be possible to determine the « forecast end date » when the status returns to « In Progress ».
In other words, if the status remains « Waiting for response », then there is nothing left to do ( only wait ) and there's therefore no more deadline.

[zdenarik]

OK, then. Thank you for explanation. Maybe in future.

[likehopper]

I've just committed the enhanced for use of a IssueCustomField in addition to IssuePriority. This week I will focus on testing and fixes. I therefore welcome your feedback!

These changes will need to be applied to the database after backup:

• ALTER TABLE sla_levels ADD COLUMN field custom_field_id BIGINT;
• ALTER TABLE sla_levels ADD CONSTRAINT sla_levels_custom_fields_fkey FOREIGN KEY (custom_field_id) REFERENCES public.custom_fields(id) ON DELETE CASCADE;
• ALTER TABLE sla_level_terms RENAME COLUMN priority_id TO priority;
• ALTER TABLE sla_level_terms ALTER COLUMN priority TEXT ;
• update sla_get_spent function

I'll modify the documentation only when everything is stabilized but you should quickly understand how to use the new functionality! Please feel free to ask me any questions to allow you to perform the tests.

[zdenarik]

Thank you for info. We will test these new features and let you know.

[likehopper]

I recommend downloading the latest version as it's enumeration based rather than list based.

[likehopper]

Have you been able to test the version I sent you? I just published a brand new stable version.

[zdenarik]

Hello @likehopper. Finally, I have started to test you new version of Redmine SLA plugin after our Redmine admin installed things by you instructions. Unfortunatelly, some issues observed:

• there is missing button "Add SLA term" in SLA terms setting
  
• after clicking on "SLA Caches" button I observe error message:
  
• after clicking on "SLA Caches spents" button I observe error message:
  

Could you give me a hand with this?! O:-) Thank you

FYI
There is report with operations what our Redmine admin made:

• Update redmine_sla from actual main (root rm70427_sla_plugin_upgrade repa redmine_plugins)
• Build image (tag 5.0.8-ceos-test)
• Helm upgrade from appropriate image
• Next in DB:

ALTER TABLE sla_levels ADD COLUMN custom_field_id BIGINT;

ALTER TABLE sla_levels ADD CONSTRAINT sla_levels_custom_fields_fkey FOREIGN KEY (custom_field_id) REFERENCES public.custom_fields(id) ON DELETE CASCADE;

ALTER TABLE sla_level_terms RENAME COLUMN priority_id TO priority;

ALTER TABLE sla_level_terms ALTER COLUMN priority set data type text;

And he has no idea what is "update sla_get_spent function". He suppose that plugin should apply this itself. Is that true?

[likehopper]

I apologize for these inconveniences. I will prioritize looking into this to fix it and add the associated tests to avoid regressions.
I would appreciate receiving the export of the database structure (with the --schema-only option).

[zdenarik]

OK, nevermind... I have contacted our Redmine admin and asked for that...

[zdenarik]

Hello @likehopper. I am very sorry, but I cannot provide the export of database because of busyness of our Redmine Admin and time consumption difficulty for do that. Are you OK with this? Thank you for understanding

[likehopper]

Yes, if you can just apply this script to rebuild the tables and functions : redmine_sla_move_from_priority_to_customfield.zip.

[likehopper]

there is missing button "Add SLA term" in SLA terms setting
In fact, it's no longer possible to add a term since the priority name depends on the custom field. You need to go to the SLA Level Index and click on the first action “Edit SLA Term” :

[zdenarik]

OK, I will try that... thx

[likehopper]

While waiting for the database structure to confirm, I think the problem is with the tables. It would be best to apply the attached script to rebuild the tables and functions : redmine_sla_move_from_priority_to_customfield.zip.
Finally, it is possible to run the script to force the cache update ( rake redmine:plugins:redmine_sla:update_sla ). Additionally, the best is to download the latest version of the code (while waiting for its stable publication and versioning).

[zdenarik]

Handed over to Redmine admin... thx

[likehopper]

Have you tested the latest available version ? Does it meet your needs ?

[zdenarik]

Hello @likehopper. Thank you for you interest. Sorry, but we have not tested it. We have more important project duties to be done. Nevertheless I am going to test it during summer holidays when our people will be on vacation. I will let you know. Thank you again for your understanding.