As per this Tweet, SQLite with EF Core might be possible in Blazor WASM .NET 6.
https://twitter.com/bricelambs/status/1491134363945570305?s=20&t=AqGHx65g7ibZ8he_K93f1A

• Investigate
• Spike
• Upgrade
• Simplify DB schema to support many integrations without DB change (JSON store for custom data instead of custom tables?)
• Final migration script from JSON to SQLite

The link to the work item should be the link for the work item, not JSON.

As a developer, I want to be able to test if new features break existing workflows.
The easiest way to test this is via UI tests.

Initial tests are done via PlayWright.

Data before automation 🤖

Display all PBI for the user.

Hi,

• Support multiple output templates e.g.

Yesterday

• ✅ Product Backlog Item 0: Add a new feature
  • ✅ - Task 1: Implement feature

Today

• ⏳ Product Backlog Item 0: Add a new feature
  • ⏳ Task 1: Implement feature

Figure: Template with emojis

• Allow users to create custom output templates

Thanks

-Brady

When we have AutoScrum open for a few days, it would be great if could just refresh Daily Scrum instead of F5 or scroll above to resubmit.

Right now, the UI is ok but it takes a lot of space and doesn't give you a lot of information.

It should have better data density.

Make the app look nice 😁

Sending emails directly from AutoScrum.

Requirements:

• Config for To, Cc and Bcc
• Email template
• Integration to O365 (possibly other emails as well)

Considerations:

• Support for emails like gmail
• A href is not sufficient to generate a well-formatted email (hence why integration is required)
• Generating email as a file that can be opened and sent. This might remove the need to integrate to various email providers.

The current favicon is the default Blazor icon, which makes it hard to find when having multiple tabs.

Under the capacity tab, we can configure days off for the team.
We should not generate daily scrum for team members on leave.

Docs:

• https://docs.microsoft.com/en-us/rest/api/azure/devops/work/teamdaysoff/get?view=azure-devops-rest-6.0
• https://docs.microsoft.com/en-us/rest/api/azure/devops/work/capacities/list?view=azure-devops-rest-6.0

On the AutoScrum page we should add a GitHub button so people can report issues and contribute to the project.

As per my conversation with @bradystroud,

• Add a copy button for the whole output
• Add a copy button for a single user - ensure it is separate from the report for copy/paste's sake - popover?

Sometimes we do work outside the Sprint board and we should be able to document that.

Work items should have a hierarchy relative to their parents.

As I developer, I want to be able to quickly create scenarios with various PBI, Sprint and other configurations for faster testing if Daily Scrum is correctly generated.

As per the SSW.SugarLearning standard, Add emojis that reflect the current state of the task:

1. In-Progress ⌛
2. Done ✅
3. Not Done ❌

Issue

When getting the data from Azure DevOps, AutoScrum will auto-add work items into the "Yesterday" and "Today" bucket.

The logic for when is yesterday is not working, which makes the following not work correctly:

• Auto-select work item you worked on yesterday
• Whether or not last workday was Friday (it would pick "Friday" on Tuesday morning on UTC+10)

Repo

• Open AutoScrum on Tuesday morning at 8 am at UTC+10 (or similar UTC timing at a different timezone)
• Submit Azure DevOps config (or auto-submit if a configuration was saved)
• Observe "Yesterday" bucket and generated report
  • Yesterday bucket will have work items started today
  • Generated report will show the last workday to be Friday

Figure: On Tuesday it should show last work day is Friday.

If you currently don’t have anything on the current sprint board assigned to you and click submit, it throws a ‘Critical Azure DevOps’ error and doesn’t provide any information for why you are getting an error.

When a team member has a blocking task, it's too all team members under blocking.

Hi,

As per my conversation with @Hona, there is no way to select the Compact and Dark theme.

I reccommend adding a switch for compact mode, that can be toggled in Dark or Default mode.

Thanks

-Brady

If the project is selected on the initial run, we should hide the configuration to put more focus on the Daily Scrum report.

Sometimes we need to generate daily scrum for yesterday or we just want to test out how it would work on a specific day.

User should be able to add and remove their PBIs into the Yesterday and Today column that will be used to generate Daily Scrum.

The purpose of this tool is to automate as much work as possible and this includes populating Yesterday/Today based on current states and when it was last changed.

Today:

• Anything that is in progress

Yesterday:

• Anything that is in progress for more than 24 hours
• Anything that was done within 24 hours

Release when merging PR into into production

The user should be able to switch between Azure DevOps accounts and projects.

Hi,

• Allow reordering of PBIs and tasks

A potential implementation is to make the cards drag and droppable. Alternativly, reording could be done in the output.

User Story

Move to MudBlazor

Acceptance Criteria

• Each AntDesign components is matched 1 to 1 for MudBlazor

VS403474: You requested 473 work items which exceeds the limit of 200

The user should be able to add a PBI even if it's not listed in the Sprint (or got by the API).

The user should be able to copy markdown Daily Scrum and paste it into an email and/or timesheet system.

Sometimes, when we work on a task/pbi, we are not assigned to the parent work item.

This means that the hierarchy isn't correct as a child needs to be displayed on the top level.

Acceptance criteria

When a task/bug is found that has a parent and parent is available on the list (probably because the user is not associated), try to find it directly via the APIs.

GitHub pages or Azure Static Web Apps (my preference due to cache control and easier maintenance).

https://github.com/william-liebenberg/AutoScrum/runs/3695170563

Access to fetch at 'https://aviancavsts.visualstudio.com/DefaultCollection/UnidadesSoporteBW/_apis/work/teamsettings/iterations?api-version=6.0&$timeframe=current' from origin 'https://autoscrum.jkdev.me' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Hi,

The "Yesterday" and "Today" buttons don't depress until another button is pressed.

• Buttons should depress after release

Figure: 'Today' button stays in pressed/hover state after release

Thanks

Hi,

The current video is great but without it, I'm unsure if users would be able to get AutoScrum up and running.
When using AutoScrum for the first time it can be a bit confusing. To help ease people into using this amazing site, I'm suggesting the following changes to help first time users.

• Add Instructions to the readme on how to get setup
• Add tooltips to each heading as shown in the image below
• Add a link back to this GitHub from the website.
• Test if a new user can get AutoScrum up and running without the use of the video

Tooltips Description examples:

Here is a first pass of the tooltips :)

Screenshot

Figure: Add tooltips on hover and click

We want to persist configuration without adding a server (for now).

When setting up a profile the placeholder for the DevOps org says to enter the organisation name or organsiation URL. Currently name works, but URL does not.

Scrum Master should be able to generate Daily Scrum for an entire team.
They also should be able to remove team members.

Atm, many Daily Scrum services are in the Blazor app but they should be in AutoScrum.Core and AutoScrum.AzureDevOps projects.

Move and refactor the services in preparation for GitHub and Azure Function support.

Hi,

There is currently no issue templates in this repo 😥. Therefore users have no clear instructions on how to report a bug or request a feature.

Please implement the following as per rule, ssw.com.au/rules/github-issue-templates

• Implement the template as per the rule above
• Test the GitHub issue templates are working
• Test the GitHub PR templates are working