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

Feature view requirements for returns #1106

Closed
wants to merge 16 commits into from

Conversation

jonathangoulding
Copy link
Collaborator

@jonathangoulding jonathangoulding commented Jun 14, 2024

Ticket - https://eaflood.atlassian.net/browse/WATER-4422

Adds a new page to allow users to view the requirements for returns.

A user can click a view link on the licence setup tab under the requirements for returns.

This page is similar to previous work done on the requirements for returns check page.

Ticket - https://eaflood.atlassian.net/browse/WATER-4422

Adds a new page to allow users to view the requirements for returns.

A user can click a view link on the licence setup tab under the requirements for returns.

This page is similar to previous work done on the requirements for returns check page.
@jonathangoulding jonathangoulding added the enhancement New feature or request label Jun 14, 2024
@jonathangoulding jonathangoulding self-assigned this Jun 14, 2024
@jonathangoulding jonathangoulding requested review from Cruikshanks, Beckyrose200, rvsiyad and Jozzey and removed request for Cruikshanks and Beckyrose200 June 17, 2024 14:42
@jonathangoulding jonathangoulding marked this pull request as ready for review June 17, 2024 14:43
@jonathangoulding jonathangoulding marked this pull request as draft June 17, 2024 14:46
@jonathangoulding jonathangoulding marked this pull request as ready for review June 17, 2024 14:56
Copy link
Member

@Cruikshanks Cruikshanks left a comment

Choose a reason for hiding this comment

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

Started adding specific comments but realised there was going to be quite a few!

But I think its because the needs for the return requirement setup journey have gotten mixed in with this. Whereas I think we can simplify things when just taking the completed record and presenting it.

This will be quicker and easier to pair on and discuss. So, we'll arrange that offline from here and progress there.

Copy link
Collaborator Author

@jonathangoulding jonathangoulding left a comment

Choose a reason for hiding this comment

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

Comments to address based on conversation

@jonathangoulding
Copy link
Collaborator Author

New PR created based on changes required - #1118

@jonathangoulding jonathangoulding deleted the feature-view-requirements-for-returns branch June 19, 2024 14:02
@jonathangoulding jonathangoulding restored the feature-view-requirements-for-returns branch June 19, 2024 14:03
@Cruikshanks Cruikshanks deleted the feature-view-requirements-for-returns branch August 19, 2024 15:16
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