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

blank screen and failure to create mockup #2033

Open
14 tasks
only1chunts opened this issue Sep 19, 2024 · 0 comments
Open
14 tasks

blank screen and failure to create mockup #2033

only1chunts opened this issue Sep 19, 2024 · 0 comments

Comments

@only1chunts
Copy link
Member

On the recent dataset uploaded 102585 #49 I made all the updates as required in the dataset admin page (added my username, the MS ID, the thumbnail image, release date, set status to "Submitted" etc..) clicked save. All fine, everything saved as expected.
I then clicked "create /reset private URL" button to generate the mockup link- it did this:

image

I then went back and tried several changes, eventually I discovered that the Status of "Submitted" was the issue! As soon as I changed that to "Curation" the create/reset button worked as expected.

User story

As a curator
I want to be able to create or reset the private mockup URL when the dataset status is "Submitted"
So that I can share the private link with people.

Acceptance criteria

Given I am on the dataset Admin page of any dataset with a status of anything EXCEPT "Published"
When I look at the bottom of the page
Then I should see a create/reset private URL button
And when I click that button it does create or reset the private URL for that dataset.

Given I am on the dataset Admin page of any dataset with status "Published"
When I look at the bottom of the page
Then I should NOT see a create/reset private URL button
NB - This is already the case, I'm just making sure its clear here that it is correct.

Additional Info

Product Backlog Item Ready Checklist

  • Business value is clearly articulated
  • Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
  • Dependencies are identified and no external dependencies would block this item from being completed
  • At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
  • This item is estimated and small enough to comfortably be completed in one sprint
  • Acceptance criteria are clear and testable
  • Performance criteria, if any, are defined and testable
  • The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

  • Item(s) in increment pass all Acceptance Criteria
  • Code is refactored to best practices and coding standards
  • Documentation is updated as needed
  • Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
  • No deviation from the team technology stack and software architecture has been introduced
  • The product is in a releasable state (i.e. the increment has not broken anything)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants