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 notification so Analysts know when they cannot change request status from "Approved" #1768

Open
3 tasks done
gabydisarli opened this issue Feb 12, 2024 · 3 comments · May be fixed by #3231
Open
3 tasks done

Add notification so Analysts know when they cannot change request status from "Approved" #1768

gabydisarli opened this issue Feb 12, 2024 · 3 comments · May be fixed by #3231
Assignees
Labels
dev issue is for the dev team Feature: 🧮 Analyst Experience Issue to improve the Analysts workflow

Comments

@gabydisarli
Copy link
Contributor

gabydisarli commented Feb 12, 2024

Issue description

In DjA we know there are certain statuses that analysts can change a request to depending on what status the request is currently in. If a request gets moved to approved, a domain information object gets created. If an analyst moves this request from approved > to in review, etc. then we will now delete the domain information object that was created so that there's no errors if the analyst then tries to move it back to approved. If however, a request gets moved to approved, and then a domain manager adds name servers, it (the associated domain) is now in Ready state. Once in Ready status, an analyst will not be allowed to change that request back to anything other than approved. Let's add a notification telling analysts that the request cannot have its status changed because the associated domain is in Ready.

Acceptance criteria

  • new notification appears at the top of a domain request (domain application) page in DjA when a domain application is joined to a domain in Ready status. This should look and behave similar to how we show analysts when contacts are joined to objects.
  • new notification copy: The status of this domain request cannot be changed because it has been joined to a domain in Ready status: <domain name>
    • NOTE: domain name is a clickable link taking analyst to the associated domain

Additional context

This work came from a suggestion Rachid made in

Slack discussion

Links to other issues

@gabydisarli
Copy link
Contributor Author

@rachidatecs FYI 👍

@vickyszuchin vickyszuchin added the dev issue is for the dev team label Feb 12, 2024
@abroddrick
Copy link
Contributor

abroddrick commented Mar 20, 2024

I think this epic should be for analyst efficiency @PaulKuykendall & @vickyszuchin

@vickyszuchin
Copy link

I'm going to mark it as "Future: Analyst experience" for now while it is in "New". Product can decide if they want it in "Analyst efficiency" when the ticket is triage. I will move it up on the "New" queue so that it can be looked at earlier. cc: @abroddrick

@PaulKuykendall PaulKuykendall changed the title Add notification for new FSM rules Add notification so Analysts know when they cannot change request status from "Approved" Mar 25, 2024
@PaulKuykendall PaulKuykendall moved this from 👶 New to 🍦 Backlog in .gov Product Board Mar 25, 2024
@katypies katypies added the Feature: 🧮 Analyst Experience Issue to improve the Analysts workflow label Aug 2, 2024
@lizpearl lizpearl moved this from 🍦 Backlog to 🎯 Ready in .gov Product Board Dec 5, 2024
@Matt-Spence Matt-Spence self-assigned this Dec 12, 2024
@Matt-Spence Matt-Spence moved this from 🎯 Ready to 🏗 In progress in .gov Product Board Dec 16, 2024
@Matt-Spence Matt-Spence moved this from 🏗 In progress to 👀 In review in .gov Product Board Dec 16, 2024
@Matt-Spence Matt-Spence linked a pull request Dec 16, 2024 that will close this issue
32 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev issue is for the dev team Feature: 🧮 Analyst Experience Issue to improve the Analysts workflow
Projects
Status: 👀 In review
Development

Successfully merging a pull request may close this issue.

5 participants