Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add bill runs setup type page to journey #802

Merged
merged 6 commits into from
Mar 11, 2024

Conversation

Cruikshanks
Copy link
Member

@Cruikshanks Cruikshanks commented Mar 11, 2024

https://eaflood.atlassian.net/browse/WATER-4375

Part of a series of changes related to replacing the create bill run journey to incorporate changes for two-part tariff

Having Add first route to bill run setup journey we can now add our first page which is where the user selects what bill run type they wish to create.

It is planned in the future that there will be 4; annual, supplementary, two-part tariff and two-part tariff supplementary. Until we have implemented two-part tariff supplementary though it is just the first 3 options.

Screenshot 2024-03-11 at 09 21 40

https://eaflood.atlassian.net/browse/WATER-4375

> Part of a series of changes related to replacing the create bill run journey to incorporate changes for two-part tariff

Having [Add first route to bill run setup journey](#801) we can now add our first page which is where the user selects what bill run type they wish to create.

It is planned in the future that there will be 4; annual, supplementary, two-part tariff and two part tariff supplementary. Until we have implemented two-part tariff supplementary though it is just the first 3 options.
@Cruikshanks Cruikshanks added the enhancement New feature or request label Mar 11, 2024
@Cruikshanks Cruikshanks self-assigned this Mar 11, 2024
This is the route, controller and view plus supporting service and presenter for the GET `/bill-runs/setup/{id}/type` page.
@Cruikshanks Cruikshanks marked this pull request as ready for review March 11, 2024 11:13
'annual',
'supplementary',
'two_part_tariff',
'two_part_tariff_supplementary'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not in the list of options on the page. is it going to be added later?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. It is coming. But I couldn't be 100% certain that is what the name of the bill run type will be when we do have to implement it.

So, on reflection, it would be better that we add this as a valid bill run type when we make the changes to support it.

We know 100% we will have to handle this bill run type in the future. But we can't be 100% whether this will be the name for it when we do.

So, to be clearer and cleaner removing this valid type for now.
@Cruikshanks Cruikshanks merged commit bf07b7b into main Mar 11, 2024
6 checks passed
@Cruikshanks Cruikshanks deleted the add-bill-runs-setup-type-page branch March 11, 2024 16:29
Cruikshanks added a commit that referenced this pull request Mar 11, 2024
https://eaflood.atlassian.net/browse/WATER-4375

> Part of a series of changes related to replacing the create bill run journey to incorporate changes for two-part tariff

This adds the second page to the setup bill run journey; select a region. This has a bit more complexity than [Add bill runs setup type page to journey](#802) because depending on the bill run type selected, we are either done or need to go to another page in the journey.
Cruikshanks added a commit that referenced this pull request Mar 12, 2024
https://eaflood.atlassian.net/browse/WATER-4375

> Part of a series of changes related to replacing the create bill run journey to incorporate changes for two-part tariff

This adds the second page to the setup bill run journey; select a region. This has a bit more complexity than [Add bill runs setup type page to journey](#802) because depending on the bill run type selected, we are either done or need to go to another page in the journey.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants