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

Improve button text and description on "last opp mine endringer" #12788

Open
Annikenkbrathen opened this issue May 10, 2024 · 2 comments
Open
Assignees
Labels
kind/bug Used when there is a defect / something is not working as it should. status/ready-for-dev Status: Used for issues that are ready for development. Has been through grooming. status/triage text/content used for issues that need som text improvements, often by ux user-need Issues describing user needs ux UX help needed

Comments

@Annikenkbrathen
Copy link

Description of the bug

Can we improve this text and change button tekst to "last opp" or "lagre" or "del endringer".
Do we need this much text? Does the user really have to validate anything, or can they just upload their latest changes? If there are conflicts, we'll notify them.

@Ildest Do you want to make a suggestion? :)

Skjermbilde 2024-05-10 kl  10 13 43

Steps To Reproduce

  1. Go to altinn Studio
  2. click on the button "last opp dine endringer"
  3. look at the text

Additional Information

No response

@Annikenkbrathen Annikenkbrathen added kind/bug Used when there is a defect / something is not working as it should. status/triage ux UX help needed status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. text/content used for issues that need som text improvements, often by ux labels May 10, 2024
@Ildest Ildest self-assigned this May 13, 2024
@Ildest
Copy link
Contributor

Ildest commented May 13, 2024

Investigated this with Andrea, and there are three connecting messages that we need to look at: the to additional are

image

image

The "conflict in application" message might need a revision too, to clearly state that you must download your changes to a zip-file before you remove your conflicting changes.

@Ildest
Copy link
Contributor

Ildest commented May 27, 2024

After @standeren´s thorough investigation of all merge conflict messages, we have uncovered five messages and revised the text for them. @Annikenkbrathen also uncovered a couple of messages that are linked to these, that we need to fix as soon as the first five have been approved and implemented. We will make a separate issue for that.

image

Suggested text:

Beskriv endringene dine og del dem

Beskriv hva du har endret før du deler endringene dine. Hvis noen andre har gjort endringer på samme sted som deg, får du beskjed.

Knapp: Del endringer

image

Suggested text and two questions:

Kunne ikke dele endringene dine, prøv på nytt.

Trengs denne meldingen egentlig?
Kommer denne meldingen bare opp ved merge conflict, eller også ved andre typer feil?

image

Suggested text:

Forslag:

En annen har endret appen på samme sted som deg

Disse endringene stemmer ikke med dine endringer. Velg Hent endringer for å få de nyeste endringene før du deler dine egne.

Knappenavn: Hent endringer + Last ned-ikon

image

Suggested text:

Det er en konflikt i appen

Noen andre har endret appen på samme sted som deg. Hvis du vil lagre det du har gjort, kan du laste ned endringene dine til en zip-fil.

Velg Slett mine endringer for å løse konflikten.

image

Suggested text and a question:

Forslag:

Vil du laste ned alle endringene dine til en zip-fil?

Hvis Del endringer ikke fungerer, kan du laste ned en zip-fil med endringene dine. Når du pakker den ut i ditt lokale Git-repo, kan du sjekke endringene dine der.

Jeg vil ha en zip-fil kun med med mine endrede filer

Jeg vil ha en zip-fil med hele repoet

Kan vi slippe å ha denne meldingen i det hele tatt? Kan vi bruke den i nr. 4 i begge tilfeller?

@nkylstad nkylstad added status/ready-for-dev Status: Used for issues that are ready for development. Has been through grooming. and removed status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. labels May 29, 2024
@nkylstad nkylstad added the user-need Issues describing user needs label Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Used when there is a defect / something is not working as it should. status/ready-for-dev Status: Used for issues that are ready for development. Has been through grooming. status/triage text/content used for issues that need som text improvements, often by ux user-need Issues describing user needs ux UX help needed
Projects
Status: Under arbeid 🚧
Status: 👷 In Progress
Development

No branches or pull requests

4 participants