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

chore: Change recommendedNextAction in process to update layoutsetname and add section to change in panel #13495

Merged
merged 6 commits into from
Sep 13, 2024

Conversation

standeren
Copy link
Contributor

@standeren standeren commented Sep 5, 2024

Description

Skjermopptak.2024-09-06.kl.13.44.53.mov

NB: Many filechanges comes from change in folder structure ✅

Related Issue(s)

  • #{issue number}

Verification

  • Your code builds clean without any errors or warnings
  • Manual testing done (required)
  • Relevant automated test added (if you find this hard, leave it and we'll help out)

@github-actions github-actions bot added area/process Area: Related to app process (e.g. signing, receipt, fill inn, payment, etc). solution/studio/designer Issues related to the Altinn Studio Designer solution. labels Sep 5, 2024
@standeren standeren changed the title Change recommendedNextAction in process to update layoutsetname and a… chore: Change recommendedNextAction in process to update layoutsetname and add section to change in panel Sep 5, 2024
@standeren standeren force-pushed the fix/allow-setting-layoutset-name-when-adding-task branch 6 times, most recently from 5285d29 to 7cec366 Compare September 9, 2024 06:51
Copy link

codecov bot commented Sep 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.16%. Comparing base (294807e) to head (1ff2adf).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #13495   +/-   ##
=======================================
  Coverage   95.15%   95.16%           
=======================================
  Files        1456     1459    +3     
  Lines       20107    20133   +26     
  Branches     2438     2439    +1     
=======================================
+ Hits        19133    19159   +26     
  Misses        868      868           
  Partials      106      106           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@standeren standeren force-pushed the fix/allow-setting-layoutset-name-when-adding-task branch 3 times, most recently from afff526 to 7712157 Compare September 9, 2024 08:11
@standeren standeren marked this pull request as ready for review September 9, 2024 08:12
@github-actions github-actions bot added the quality/testing Tests that are missing, needs to be created or could be improved. label Sep 9, 2024
@Jondyr Jondyr self-requested a review September 10, 2024 09:02
Copy link
Member

@Jondyr Jondyr left a comment

Choose a reason for hiding this comment

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

Good job 👍 I have two things for you to consider:

@ErlingHauan
Copy link
Contributor

ErlingHauan commented Sep 11, 2024

Nice work 😄

@Konrad-Simso and I tested this together.

Function

Functionally it works great. It makes sense that this "recommended next action" should only appear for process steps that have layout sets connected. We also checked that the code in Gitea changed as expected.

Language

We have some considerations about the language.
Maybe we should use another word than utforming here, as it may become confusing when we change the name of Lage to Utforming?

bilde

Suggestion:

Gi sidegruppen et navn

Når du lager en ny oppgave, blir også en sidegruppe laget. Du finner lettere igjen sidegruppen på Lage-siden, hvis du gir den et eget navn. Hvis du velger Hopp over, får sidegruppen et tilfeldig navn. Du kan endre navnet senere.


And in the picture below, maybe change Utforming av Task_1: form to Navn på sidegruppe: form?

Skjermbilde 2024-09-11 103036

@standeren
Copy link
Contributor Author

standeren commented Sep 11, 2024

Nice work 😄

@Konrad-Simso and I tested this together.

Function

Functionally it works great. It makes sense that this "recommended next action" should only appear for process steps that have layout sets connected. We also checked that the code in Gitea changed as expected.

Language

We have some considerations about the language. Maybe we should use another word than utforming here, as it may become confusing when we change the name of Lage to Utforming?

bilde

Suggestion:

Gi sidegruppen et navn
Når du lager en ny oppgave, blir også en sidegruppe laget. Du finner lettere igjen sidegruppen på Lage-siden, hvis du gir den et eget navn. Hvis du velger Hopp over, får sidegruppen et tilfeldig navn. Du kan endre navnet senere.

And in the picture below, maybe change Utforming av Task_1: form to Navn på sidegruppe: form?

Skjermbilde 2024-09-11 103036

@ErlingHauan @Konrad-Simso
I believe we landed on avoiding the word "Sidegruppe" based on the sketches from @Annikenkbrathen
https://www.figma.com/design/l1Gs7lZ1asnfpHV4soGszo/Studio-design-system-og-konsept?node-id=1312-1709&node-type=canvas&m=dev 🫣

There is also a slack thread where this were discussed;
https://digdir.slack.com/archives/C077KTTCBSS/p1725612681723129
But I think we can iterate on it perhaps?

@ErlingHauan
Copy link
Contributor

@ErlingHauan @Konrad-Simso I believe we landed on avoiding the word "Sidegruppe" based on the sketches from @Annikenkbrathen https://www.figma.com/design/l1Gs7lZ1asnfpHV4soGszo/Studio-design-system-og-konsept?node-id=1312-1709&node-type=canvas&m=dev 🫣

There is also a slack thread where this were discussed; https://digdir.slack.com/archives/C077KTTCBSS/p1725612681723129 But I think we can iterate on it perhaps?

@standeren I see your point, but I don't think we have landed on avoiding Sidegruppe yet. I think we were supposed to discuss it this friday 🤔

I agree that we can iterate, but Gi utformingen et navn is a bit confusing to me. When reading that text, I don't understand exactly what I am naming. Maybe it would confuse our users as well 😬

What do you think about changing it to Gi oppgaven et navn to avoid the term Sidegruppe, and iterate on that?

@standeren
Copy link
Contributor Author

@ErlingHauan @Konrad-Simso I believe we landed on avoiding the word "Sidegruppe" based on the sketches from @Annikenkbrathen https://www.figma.com/design/l1Gs7lZ1asnfpHV4soGszo/Studio-design-system-og-konsept?node-id=1312-1709&node-type=canvas&m=dev 🫣
There is also a slack thread where this were discussed; https://digdir.slack.com/archives/C077KTTCBSS/p1725612681723129 But I think we can iterate on it perhaps?

@standeren I see your point, but I don't think we have landed on avoiding Sidegruppe yet. I think we were supposed to discuss it this friday 🤔

I agree that we can iterate, but Gi utformingen et navn is a bit confusing to me. When reading that text, I don't understand exactly what I am naming. Maybe it would confuse our users as well 😬

What do you think about changing it to Gi oppgaven et navn to avoid the term Sidegruppe, and iterate on that?

Hm, I see your point, but oppgave is referring to the task, which is not correct either 🤔

@ErlingHauan
Copy link
Contributor

Hm, I see your point, but oppgave is referring to the task, which is not correct either 🤔

Agreed 😅
In this case it's not easy to avoid Sidegruppe... Maybe @Ildest has some thoughts on this?

@standeren
Copy link
Contributor Author

Hm, I see your point, but oppgave is referring to the task, which is not correct either 🤔

Agreed 😅 In this case it's not easy to avoid Sidegruppe... Maybe @Ildest has some thoughts on this?

Yup 😅 She has already given some input in the slack thread tho, but at that time your inputs were not shared so she might have other opinions now 😄

@standeren standeren force-pushed the fix/allow-setting-layoutset-name-when-adding-task branch from b0ba3b8 to 2164fb8 Compare September 12, 2024 09:04
@Ildest
Copy link
Contributor

Ildest commented Sep 12, 2024

@standeren and @ErlingHauan: I think we need to use sidegruppe here for now, and change it later if we change the term. Suggestion based on Erling´s:

Gi sidegruppen et navn
Når du lager en ny oppgave, får du også automatisk en sidegruppe. Gi gruppen et navn, så du lettere finner den igjen på Utforming-siden. Hvis du velger Hopp over får sidegruppen et tilfeldig navn, men det kan du endre senere.

Veldig bra jobb i utganspunktet på denne meldingen dere - kudos!

@standeren
Copy link
Contributor Author

Når du lager en ny oppgave, får du også automatisk en sidegruppe. Gi gruppen et navn, så du lettere finner den igjen på Utforming-siden. Hvis du velger Hopp over får sidegruppen et tilfeldig navn, men det kan du endre senere

Den er god! Takk for rask respons 💪
Men én ting; bare så det er klart så får man ikke alltid en automatisk opprettet sidegruppe når man oppretter et steg -> det er kun for visse steg-typer. Men på en annen side så vil jo denne meldingen bare dukke opp for de stegtypene som trigger automatisk opprettelse av et layoutset så det er kanskje greit å ordlegge seg sånn uansett? 😅

@ErlingHauan
Copy link
Contributor

ErlingHauan commented Sep 12, 2024

Tre forslag:

Når du lager en ny oppgave av denne typen, får du også automatisk en sidegruppe. Gi gruppen et navn, så du lettere finner den igjen på Utforming-siden. Hvis du velger Hopp over får sidegruppen et tilfeldig navn, men det kan du endre senere

Når du lager en ny utfyllingsoppgave, får du også automatisk en sidegruppe. Gi gruppen et navn, så du lettere finner den igjen på Utforming-siden. Hvis du velger Hopp over får sidegruppen et tilfeldig navn, men det kan du endre senere

Når du lager en ny betalingsoppgave, får du også automatisk en sidegruppe. Gi gruppen et navn, så du lettere finner den igjen på Utforming-siden. Hvis du velger Hopp over får sidegruppen et tilfeldig navn, men det kan du endre senere

De to siste medfører vel litt endring i koden, så det er kanskje ikke verdt å gjøre det i denne omgangen?

Veldig gode forslag å spesifisere på denne måten i de tre meldingen - du tar dette med skriving fort @ErlingHauan :-D. Jeg tenker at det oppfyller et brukerbehov å få en god melding som også forteller konteksten, så kjør på med kodeendringer hvis det ikke tar en uke og de som sjefer over koden ikke har noe imot det :-D.

Og så må vi slutte å si steg og holde oss til oppgave, og kaste ut layoutset(t) og si sidegruppe, så vi får en litt enklere hverdag i kommunikasjonen oss imellom, ha ha!

Copy link
Contributor

@ErlingHauan ErlingHauan left a comment

Choose a reason for hiding this comment

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

Godt jobba 👏
Ikke meningen å være en masekopp 😄

frontend/language/src/nb.json Outdated Show resolved Hide resolved
@standeren standeren force-pushed the fix/allow-setting-layoutset-name-when-adding-task branch from 8ff914e to 1ff2adf Compare September 12, 2024 10:20
@standeren standeren merged commit aec2c65 into main Sep 13, 2024
9 checks passed
@standeren standeren deleted the fix/allow-setting-layoutset-name-when-adding-task branch September 13, 2024 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/process Area: Related to app process (e.g. signing, receipt, fill inn, payment, etc). quality/testing Tests that are missing, needs to be created or could be improved. solution/studio/designer Issues related to the Altinn Studio Designer solution.
Projects
None yet
5 participants