Documenting a minor or major modification [#2664620]

I'm not finding a way to document the request or issuance of minor or major permit modifications and the reasons for the modification. Can these be added? Also, a major modification involves a permit number change with the addition of a 1 after GW instead of a 0: GW1003500 rather than GW0003500.

This might need a post permitting tab under the permit page to allow other issues too. A meeting option is needed too to document meetings or calls, etc.

Comments

Comment #1

8 February 2016 at 13:54

cetisdale created an issue. See original summary.

Comment #2

robertwb CreditAttribution: robertwb commented 8 February 2016 at 14:21

We obviously need to add the event to mark the mod, and the permit ID appendage is just an edit to the permit ID?

Comment #3

c_thomas CreditAttribution: c_thomas commented 8 February 2016 at 15:29

Assigned:

Unassigned

» c_thomas

I'll suggest creating two new Permitting even variables for the mods. Minor Modification and Major Modification? If that sounds reasonable, I'll create them and test to make sure it works.

Comment #4

cetisdale CreditAttribution: cetisdale commented 8 February 2016 at 16:38

I'm not sure what an even variable is but it sounds like a start.
But a new tab (variable?) that provided a space for post-permit issuance actions would be helpful and these two events could reside here.
Can there be other events here, such as meetings, submittals, and a comment field to note what the modification is for that would show up on the Permit sheet.

Comment #5

robertwb CreditAttribution: robertwb commented 8 February 2016 at 18:37

The variable approach is definitely a start- in brief Erinn, it's just creating a timestamp of a very simple event that says "X happend to this permit". I have to check my notes on the data model, but I believe we should handle the permit mods as a "submittal" which is linked back to the permit. For major versus minor, we need to talkto Craig, does he view a major mod essentially as a new permit, in which case it would link back to the old one via a shared submittal and timeseties events. I think we don't want to link them based on a permit ID extension however as was done in the past, but again, we will see whst Craig wants program wide since all permits share this sort of happening.