Skip to content
Issues
Issue
Summary
Issue url
Assignee
Description
Column 6
Column 7
6
My laptop won’t start!
20
Evaluate and incorporate user feedback
Polly Rose
Gather user feedback through surveys and interviews, and incorporate the insights into refining the matching algorithm to better meet the specific needs of dog owners.
21
Improve accuracy of breed recognition
Lola Tseudonym
Enhance the breed recognition algorithm to improve the accuracy of identifying dog breeds for more precise matching.
22
Implement machine learning model updates
Lola Tseudonym
Update the machine learning model used for dog walker matching based on user feedback and data analysis.
23
Improve accuracy of breed recognition
Lola Tseudonym
Enhance the breed recognition algorithm to improve the accuracy of identifying dog breeds for more precise matching.
24
Refactor code for better performance
Lola Tseudonym
Refactor the codebase to optimize performance and reduce the time required for matching dog walkers with dogs.
25
Optimize algorithm for large datasets
Lola Tseudonym
Enhance the AI algorithm to handle larger datasets more efficiently and accurately, ensuring scalability as the user base grows.
26
Implement GPS tracking functionality
Alan Chowansky
Integrate GPS tracking into the WalkWise app to provide real-time location updates for both dog owners and dog walkers.
27
Develop emergency alert system
Alan Chowansky
Design and implement an emergency alert system that allows dog walkers and dog owners to quickly notify each other in case of emergencies or unexpected situations during walks.
28
Implement push notifications
Polly Rose
Set up push notification functionality to send alerts and notifications to dog owners, providing them with updates on their dog’s walk status and any important information.
29
Create reporting system for walk metrics
Polly Rose
Develop a reporting system that collects and presents walk metrics such as distance covered, duration, and bathroom breaks, providing insights to dog owners about their dog’s activity.
30
Enhance photo and video sharing!!
Lola Tseudonym
Improve the photo and video sharing feature to allow dog walkers to capture and share moments from the walks with dog owners, enhancing the overall user experience.
31
Implement interactive map functionality
Alan Chowansky
Integrate an interactive map into the WalkWise app and website, allowing dog owners to track their dog’s walk route in real-time.
32
Enhance scheduling feature
Alan Chowansky
Improve the scheduling feature, allowing dog owners to easily schedule and manage dog walking services based on their preferences and availability.
33
Create detailed walk reports
Lola Tseudonym
Develop a feature that generates detailed walk reports, including information on distance covered, time spent walking, bathroom breaks, and any noteworthy incidents during the walk.
34
Implement in-app messaging system
Lola Tseudonym
Set up an in-app messaging system that enables seamless communication between dog owners and dog walkers for any necessary updates or inquiries.
35
Improve user interface and experience
Alan Chowansky
Enhance the overall user interface and experience of the WalkWise app and website, making it more intuitive, visually appealing, and user-friendly.
36
Implement identity verification system
Alan Chowansky
Develop an identity verification system for dog walkers, ensuring that only verified and trustworthy individuals can join the WalkWise platform.
37
Enhance emergency response protocols
Alan Chowansky
Establish and improve protocols for handling emergency situations during dog walks, ensuring swift and appropriate responses from dog walkers and effective communication with dog owners.
38
Implement data privacy enhancements
Polly Rose
Strengthen data privacy measures, including encryption and secure storage, to safeguard user information and ensure compliance with privacy regulations.
39
Enhance compatibility with pet wearables
Alan Chowansky
Improve integration with pet wearables, such as GPS trackers and health monitors, to provide dog owners with real-time insights into their dog’s well-being during walks.
40
Develop compatibility with fitness trackers
Polly Rose
Integrate WalkWise with popular fitness trackers, allowing dog owners to track their dog’s activity and health data during walks.
41
Enable automated door access for dog walkers
Alan Chowansky
Integrate WalkWise with home automation systems to provide dog walkers with automated access to clients’ homes during scheduled walks.
42
Implement smart home integration for seamless experiences
Polly Rose
Enable integration with smart home devices, allowing dog owners to control home features such as lights, temperature, and security systems during dog walks.
43
Develop compatibility with automated feeding systems
Lola Tseudonym
Integrate WalkWise with automated pet feeding systems, enabling dog owners to schedule and control feeding times remotely.
44
AI Algorithm Optimization
This epic focuses on enhancing the AI algorithms used by WalkWise to match professional dog walkers with dogs based on their specific needs. It aims to improve the accuracy and efficiency of the matching process.
45
Real-time Monitoring and Alerts
This epic aims to enhance the real-time monitoring capabilities of WalkWise, including GPS tracking, emergency alerts, and notifications for pet owners and dog walkers.
46
Mobile App and Website Enhancements
This epic focuses on improving the user experience and functionality of the WalkWise mobile app and website, including features like easy scheduling, interactive maps, and detailed walk reports.
47
Safety and Security Enhancements
This epic addresses the continuous improvement of safety and security measures in the WalkWise ecosystem, including identity verification, emergency response protocols, and data privacy enhancements.
48
Integration with Smart Devices
This epic focuses on integrating WalkWise with smart devices such as pet wearables and home automation systems, enabling compatibility with fitness trackers, automated door access, and smart home integration.
55
The flux capacitor will allow the DeLorean to travel through time
We are going to need to steal some uranium for this one.
83
Upgrade latest version
Jasmine Jones
New test
new header
Trying out new description
header for colors
{color:#36b37e}CEnter aligned stuff{color}
||A||B||X||S||
|one|two|three|four|
|blue|green|pink|cyan|
console.log("hello")
84
That I'm working on need to fix
😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇😇👩
92
Bioinformatics to build DNA variant calling and characterization algorithms
Hari Sivaramakrishnan
108
Integration with Smart Devices
Integrate WalkWise with 3 smart devices such as pet wearables and home automation systems.
109
AI Algorithm Optimization
Improve the accuracy and efficiency of the matching process and reduce rejected walk requests by 30%
144
Filter control doesn't work from column menu (nothing gets added)
Former user
153
Instructions for deleting this sample board and project are in the description for this issue >> Click the "SAMPLE-17" link and read the description tab of the detail view for more
Former user
To delete this Sample Project (must be performed by a user with Administration rights)
To delete the Sample Project workflow and workflow scheme (must be performed by a user with Administration rights)
To delete this Board (must be performed by the owner of this Board or an Administrator)
154
As a team, we can finish the sprint by clicking the cog icon next to the sprint name above the "To Do" column then selecting "Complete Sprint" >> Try closing this sprint now
155
As a scrum master, I can see the progress of a sprint via the Burndown Chart >> Click "Reports" to view the Burndown Chart
156
As a user, I can find important items on the board by using the customisable "Quick Filters" above >> Try clicking the "Only My Issues" Quick Filter above
Former user
Creating Quick Filters
You can add your own Quick Filters in the board configuration (select Board > Configure)
157
As a developer, I can update details on an item using the Detail View >> Click the "SAMPLE-13" link at the top of this card to open the detail view
Former user
Editing using the Detail View
Many of the fields in the detail view can be inline edited by simply clicking on them.
For other fields you can open Quick Edit, select “Edit” from the cog drop-down.
158
When the last task is done, the story can be automatically closed >> Drag this task to "Done" too
159
Update task status by dragging and dropping from column to column >> Try dragging this task to "Done"
Former user
160
As a developer, I can update story and task status with drag and drop (click the triangle at far left of this story to show sub-tasks)
Former user
161
As a developer, I'd like to update story status during the sprint >> Click the Active sprints link at the top right of the screen to go to the Active sprints where the current Sprint's items can be updated
162
As a product owner, I'd like to include bugs, tasks and other issue types in my backlog >> Bugs like this one will also appear in your backlog but they are not normally estimated
Estimation of Bugs
Scrum teams do not normally apply story point estimates to bugs because bugs are considered to be part of the ongoing work that the team must deal with (i.e the overhead). If you view the story points completed in a sprint as a measure of progress, then bugs also have no value because they do not deliver anything additional to the customer.
However, you can apply estimates to bugs if you wish by configuring the “Story Points” field to apply to other Issue Types (by default it only applies to Stories and Epics). Some more information on this is in the .
163
This is a sample task. Tasks are used to break down the steps to implement a user story
Former user
164
As a scrum master, I'd like to break stories down into tasks we can track during the sprint >> Try creating a task by clicking the Sub-Tasks tab in the Detail View on the right
Task Breakdown
Many teams choose to break down user stories into a set of tasks needed to implement the story. They then update the status of these tasks during a sprint to track progress. The completion of the last task signals the end of the story.
You can add sub-tasks to a story on the sub-task tab (folder icon) above.
165
As a team, I'd like to commit to a set of stories to be completed in a sprint (or iteration) >> Click "Create Sprint" then drag the footer down to select issues for a sprint (you can't start a sprint at the moment because one is already active)
Starting a Sprint
During the Planning Meeting the team will examine the stories at the top of the backlog and determine which they can commit to completing during the coming sprint. Based on this information the Product Owner might break down stories into smaller stories, adjust story priorities or otherwise work with the team to define the ideal sprint outcome. When the sprint is started the stories are moved into the sprint backlog.
166
As a team, I'd like to estimate the effort of a story in Story Points so we can understand the work remaining >> Try setting the Story Points for this story in the "Estimate" field
This story is estimated at 5 Story Points (as shown in the “Estimate” field at the top right of the Detail View).
Try updating the Story Point estimate to 4 by clicking on the “Estimate” then typing.
Estimating using Story Points
Because the traditional process of estimating tasks in weeks or days is often wildly inaccurate, many Scrum teams estimate in Story Points instead. Story Points exist merely as a way to estimate a task’s difficulty compared to some other task (for example, a 10-point story would probably take double the effort of a 5-point story). As teams mature with Scrum they tend to achieve a consistent number of Story Points from Sprint to Sprint – this is termed the team’s velocity. This allows the Product Owner to use the velocity to predict how many Sprints it will take to deliver parts of the backlog.
Many teams use Planning Poker to achieve consensus on Story Point estimates.
Using Other Estimation Units
You can configure JIRA Software to use time-based estimates if you wish. In the configuration for the board, on the “Estimation” tab, select “Original Time Estimate” as your Estimation Statistic. If you also wish to track the time used during the Sprint, select “Remaining Estimate and Time Spent” to enable Time Tracking in JIRA Software.
167
As a product owner, I'd like to rank stories in the backlog so I can communicate the proposed implementation order >> Try dragging this story up above the previous story
About the Product Backlog
The backlog is the source of truth for the order of work to be completed. It is expected that the Product Owner will work with the team to make sure that the backlog represents the current approach to delivering the product. JIRA Software makes it easy to prioritise (rank) Stories by dragging them up and down the backlog.
168
As a product owner, I'd like to express work in terms of actual user problems, aka User Stories, and place them in the backlog >> Try creating a new story with the "+ Create Issue" button (top right of screen)
When you click “+ Create Issue” you will be asked for the correct project (select “Sample Project”) and Issue Type (select “Story”).
About User Stories
The Scrum methodology drops traditional software requirement statements in favour of real world problems expressed as User Stories. Stories describe the task a particular user is trying to achieve and its value. They are typically of the form “As a (role) I want (something) so that (benefit)”. This approach focuses the team on the core user need rather than on implementation details.
Stories are “placeholders for a conversation” – they do not need to be especially detailed since it is expected that the team will work together to resolve ambiguity as the story is developed.
Stories to be implemented in the future are stored in the Product Backlog. The backlog is ranked by the Product Owner so that the next items to be completed are at the top.
169
As an Agile team, I'd like to learn about Scrum >> Click the "SAMPLE-1" link at the left of this row to see detail in the Description tab on the right
About Scrum
Scrum is an iterative approach to Agile software development. The methodology has been around since the 1980s but was popularised by Jeff Sutherland and Ken Schwaber.
Scrum breaks the development of a product down in to discrete iterations (termed Sprints) that each deliver functionality that could potentially be shipped to users.
The Scrum Alliance offers an excellent that provides an overview of key Scrum concepts, stakeholders, processes and artefacts.
202
Testing and quality assurance.
Polly Rose
Conduct testing and quality assurance to ensure smooth integration and compatibility with different veterinary clinic systems.
203
Develop API integration
Polly Rose
Develop API integration with veterinary clinics’ systems to enable seamless data exchange.
204
Implement secure data sharing protocols
Lola Tseudonym
Implement secure data sharing protocols to ensure the privacy and integrity of pet health data.
205
Create user-friendly interface
Lola Tseudonym
Create a user-friendly interface for veterinarians to access and review pet health data from PetPulse.
206
Training and support
Alan Chowansky
Provide training and support for veterinary clinic staff on how to effectively use the integrated PetPulse system.
207
Conduct user research
Alan Chowansky
Conduct user research and gather feedback to identify pain points and areas for improvement in the current app interface.
208
Create wireframes and prototypes
Alan Chowansky
Create wireframes and prototypes to visualize the new user interface design and gather user feedback.
209
Collaborate with UX designers
Alan Chowansky
Collaborate with UX designers to implement the new design, ensuring it is visually appealing and intuitive for users.
210
Test the redesigned user interface
Alan Chowansky
Test the redesigned user interface with a group of users to gather feedback on usability and make necessary adjustments.
211
Final testing and quality assurance
Polly Rose
Conduct a final round of testing and quality assurance to ensure a smooth transition to the new user interface.
212
Implement encryption protocols
Alan Chowansky
Implement encryption protocols to secure pet health data during transmission and storage.
213
Enhance user authentication mechanisms
Alan Chowansky
Enhance user authentication mechanisms to prevent unauthorized access to sensitive data.
214
Conduct regular security audits
Polly Rose
Conduct regular security audits to identify and address potential vulnerabilities in the PetPulse system.
215
Collaborate with cybersecurity experts
Lola Tseudonym
Collaborate with cybersecurity experts to ensure compliance with industry best practices and regulations.
216
Educate users on data security
Polly Rose
Educate users on best practices for data security and provide resources for them to protect their personal information.
217
Implement behavior monitoring functionality
Polly Rose
Implement behavior monitoring functionality to help pet owners identify and address behavioral issues.
218
Develop social feature
Polly Rose
Develop a social feature that allows pet owners to connect with other pet owners and share their pet’s achievements and milestones.
219
Develop integration with smart home devices
Alan Chowansky
Develop integration with smart home devices to enable pet owners to control and monitor their pets’ environment remotely.
220
Create medication administration feature
Polly Rose
Create a feature for pet owners to schedule and track medication administration for their pets.
221
Enable integration with pet food brands
Alan Chowansky
Enable integration with popular pet food brands to provide personalized nutrition recommendations based on pet health data.
222
Analyze and evaluate current AI algorithms
Polly Rose
Analyze and evaluate the current AI algorithms used for matching professional dog walkers and dogs.
223
Identify areas for improvement
Lola Tseudonym
Identify areas for improvement in the matching process, such as reducing false positives and improving accuracy.
224
Optimize the algorithm
Polly Rose
Optimize the algorithm to consider additional factors, such as dog breed, size, and specific needs.
225
Testing and validation
Polly Rose
Conduct testing and validation to ensure the optimized algorithm performs better than the previous version.
226
Monitor and analyze performance
Polly Rose
Monitor and analyze the performance of the optimized algorithm to make further adjustments and improvements.
227
AI Algorithm Optimization
This epic focuses on enhancing the AI algorithms used by WalkWise to match professional dog walkers with dogs based on their specific needs. It aims to improve the accuracy and efficiency of the matching process.
228
New Feature Development
This epic involves the development of new features for the PetPulse app, such as integration with smart home devices and behavior monitoring. It aims to enhance the functionality and user experience of the app.
229
Data Security Enhancement
This epic focuses on enhancing the data security measures implemented in the PetPulse system. It includes implementing encryption protocols, secure user authentication, and regular security audits to protect user data.
230
User Interface Redesign
This epic aims to redesign the user interface of the PetPulse app to improve its visual appeal, ease of use, and overall user experience. It involves conducting user research, creating wireframes, and implementing the new design.
231
Integration with Veterinary Clinics
Matt Hudson
This epic focuses on integrating PetPulse with veterinary clinics’ systems to facilitate seamless communication and collaboration between pet owners and veterinarians. It aims to streamline the process of sharing health data and receiving professional advice.
233
What's next?
Former user
h4. Now it’s your turn!
{color:#707070}Now, it is your turn to create your first task. Click the ‘Create’ button and get your project started. {color}
h4. If you are a JIRA Core administrator, you can create and customize projects for your organization.
Keyboard shortcuts
234
Keyboard shortcuts
Matt Hudson
h4. Working faster
{color:#707070}!Keyboard.png! Are you a fan of keyboard shortcuts? We are too! Press !questionmark.png! to see the list.
Here are three of our favourites that you might like to try:{color}
Searching for Information
What’s next
235
Searching for information
Former user
h4.Searching for Information
{color:#707070}Use the Search bar in the top right to quickly find a particular task.
For more advanced searches, click ‘Search for issues’ under the Issues menu.
{color}
Next:
{color:#707070}Previous:{color}
Keyboard shortcuts
Editing tasks
236
Editing tasks
Matt Hudson
h4. Editing tasks
{color:#707070}Hover over the content you want to edit and make the change. Click the checkmark and you’re done! You can also edit using keyboard shortcuts or by clicking the ‘Edit’ button. And don’t forget to assign the task to someone. {color}
h4. Commenting
{color:#707070}You can add comments to a task below. Comments are a great way to communicate with your team and stay informed. Plus, you can notify specific team members by using @mentions.
{color}
JiraImage !Comment.png!
Next:
{color:#707070}Previous:{color}
Searching
Workflows and Statuses
237
Workflows and statuses
Former user
JiraImage !Workflow.png|align=left!
h4. Workflows - What you need to know
{color:#707070}Workflows define steps to get a task to done. To see the workflow this tasks goes through, click on ‘View Workflow’ above. {color}
h4. Status
{color:#707070} A status represents the “state” of a task at a specific point in your workflow. The current status of your task can be viewed in the ‘Details’ section above. Once you’re ready to move to the next step, click on the appropriate transition button. {color}
Next:
{color:#707070}Previous:{color}
Editing tasks
This is your first task.
292
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Former user
293
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Former user
294
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Former user
295
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Former user
296
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Former user
297
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Former user
298
Instructions for deleting this sample board and project are in the description for this issue >> Click the "KS-10" link and read the description tab of the detail view for more
Former user
To delete this Sample Project (must be performed by a user with Administration rights)
To delete the Sample Project workflow and workflow scheme (must be performed by a user with Administration rights)
To delete this Board (must be performed by the owner of this Board or an Administrator)
299
As teams develop with Kanban they get better at reducing average resolution time (aka Cycle time). The Control Chart in the Reports shows this information
Former user
300
Filters at the top of the board allow you to quickly cut down the shown items >> Try clicking the "Recently Updated" to hide work items not updated in the past day
Former user
Creating Quick Filters
You can add your own Quick Filters in the board configuration (select Board > Configure)
301
... so 2 work items violate the limit and cause the column to be highlighted
Former user
Setting Constraints
You can set limits (constraints) for columns on this board by editing the board’s configuration (select Board > Configure)
303
Work items flow through different stages from left to right >> Try dragging this card to "Selected for Development"
Former user
Creating Columns
You can also add columns to this board by editing its configuration (select Board > Configure)
304
Work items are ranked in priority order (from top to bottom) >> Try dragging this card over the card below to rank its priority lower
Former user
305
Add work items with "+ Create Issue" at the top right of the screen >> Try adding a new card now
Former user
Creating Issues
When you click “+ Create Issue” you will be asked for the correct project (select “Kanban Sample”).
306
Kanban boards are often divided into streams of work, aka Swimlanes. By default, Kanban boards include an "Expedite" swimlane for items marked with the highest priority (like this one)
Former user
Creating Swimlanes
You can create your own Swimlanes for this board by editing its configuration (select Board > Configure)
307
Kanban cards represent work items >> Click the "KS-1" link at the top of this card to show the Detail view - there's more on Kanban in the 'Description' section
Former user
About Kanban
is part of the Toyota Lean Manufacturing methodology but was popularised for use in IT by David Anderson. Broadly speaking it aims to optimize outcomes by:
To close this view of this task (called the Detail view), click the cross in the top right corner
313
Jira sync is constantly modifying cloumn value formats of columns in at least one doc
Oleg Vaskevich
FWIW this doc is not very active, so the top priority is to see if this is affecting all docs with Jira sync.
This caused snapshots to lag until pausing the data sink.
Once fixed we need to resume the sink.
317
Handle case where credentials no longer work / user disconnected on GitHub side
Brett Hobbs
Should just flag token as bad and mark as DISCONNECTED
332
Admin: add metrics for data sources
Nigel Ellis
Several things here:
333
Figure out usage and next steps
Eric Koleda
Document outlines a full path for rich text in cells steps 4-9 . Evaluate when we should do this work…
334
Investigate direct @ref/hyperlink support for values within Ranges
Eric Koleda
***** evaluate if this is worthwhile *****
Optional step (I do not recommend as very little of this work carries forward and it will make it a lot more work to migrate away from this to the longer term plan, but it is possible to do this):
VK: if we take the approach that at-refs, hyperlinks and images are not formulas at all but simply static objects (with at-ref name-changed handled by UI), we can implement this plan and stick with it in the longer term. If we want to treat these similar to controls though (and treating them similar to controls will unify our code considerably), it might make sense to not take this dead-end route.
335
Improve formula support for Ranges values
Nigel Ellis
Issues:
Proposal: Scrub all string-based formulas to find appropriate implementations with rich text and do not provide access to the at-refs in the short-term. Some formulas may be painful to implement well but our string coercion is a reasonable fallback for those.
336
Finish initial PR from VK and add tests
Nigel Ellis
337
Trello data sink settings dialog time/dates are missing
Oleg Vaskevich
Add initial sync time on the server as “last sync time”. Remove next sync and sync from date fields for this data source.
338
Trello board names are missing from the data sinks settings dialog
Oleg Vaskevich
Also missing from the server datasource payload generated in get_data_sinks.
339
Jira project names missing from the data sink settings dialog
Oleg Vaskevich
We need to add these on the server side in the datasource payload somewhere.
340
Webhook settings dialog doesn't show last push information
Oleg Vaskevich
Missing from the server data.
344
Handle user's revoking tokens/deleting target datasource (repo/project/board/etc.)
Oleg Vaskevich
347
Support RichEdit in Cells
Nigel Ellis
An outline of the approach for full support can be found in
For this initial work we plan to tackle simple formatting of cell data (bold, italics, highlight, etc), ensure string based formulas work correctly over Ranges values and investigate HYPERLINK support within cells.
351
Jira full sync needs to schedule follow up fetches ASAP when > 1000 issues
Brett Hobbs
Since we limit fetches and pushes to a single page of jira issues we should detect when we’ve fetched a full page and schedule a follow up fetch rather than scheduling one an hour in the future.
352
Upsert key fails to identify match when an issues moves between projects in Jira
Brett Hobbs
Carissa from GoFundMe reported that when moving an issue from one project to another it ends up appearing in both projects. Looks like the cause is that we use the ‘key’ field as the upsert key. Id would probably be better but we need to confirm it doesn’t change too and is unique across projects.
355
Remove uniqueness constraint on deleted datasource and allow creating new ones
Oleg Vaskevich
This will allow us to have proper integration tests and a prod dev test script, where we can test the entire flow from creating a new datasource to testing it, all under the same user account.
363
Datasource Integration Testing
Oleg Vaskevich
Test datasources setup end-to-end:
This will require some investigation to determine the best infra layering to create in order to reduce duplication across different sources.
364
Admin: generic search
Add generic search box to admin panel to enable searching by guid for anything related - ex: datasourceId, workflowId, webhookId, …
365
Admin: Move User/Domain mapping of Experiments into Admin console
Similar to user/domain whitelisting, enable default experiments mapping via. whitelist panel.
366
Admin: Add diagnostics / key state data for data source
It’s very hard to see if a datasource is syncing and if not why not:
367
Admin: Add user accounts profile view in admin console
Nigel Ellis
Link all views with userId to the user profile.
368
Improve supportability of Datasources in Admin Service
Nigel Ellis
Improve our overall ability to support datasources.
369
Add Pingdom /healthz endpoint for important datasource workflows
Brett Hobbs
For example /workflow-healthz?workflow=fetchData then wire this up to Pingdom so we can check on basic health.
370
Workflows: improve logging for better offline diagnostics
Brett Hobbs
Also consider adding default Loggly search links to admin console.
372
GitHub client silently supresses 403's and causes down stream failures
Jason Stowe
If we get a non 200 we should throw and return the body or message in the body
Sample 403 is:
{
“message”: “API rate limit exceeded for jenkins-highfive.”,
“documentation_url”: “”
}
373
Add support for adding new columns to existing documents when we update the schema for provider
If we add support for new columns in a data source, add support for applying this schema to the existing source then schedule a full fetch to get them populated.
384
Jira integration busted on HEAD
Nigel Ellis
[error:2016-10-28T16:35:04.826+00:00] /oauth-provider-handshake?state=%7B%22continueTo%22%3A%22%2Foauth-provider-done%22%2C%22requestId%22%3A%22fake-request-id%22%2C%22provider%22%3A%22jira%22%2C%22custom%22%3A%7B%22providerUrl%22%3A%22https%3A%2F%%22%7D%7D&oauth_token=a0avxnrYzmNkzKYcOEpm7FQLkBoxbwni&oauth_verifier=HRo0R3 error status 500: HttpError: undefined is not a function
at promise.join (/krypton/experimental/modules/server/authentication/src/jira_oauth.js:54:9)
at eval (eval at (/krypton/experimental/node_modules/bluebird/js/main/join.js:23:16), :6:20)
at tryCatcher (/krypton/experimental/node_modules/bluebird/js/main/util.js:26:23)
at Holder.checkFulfillment (/krypton/experimental/node_modules/bluebird/js/main/join.js:51:40)
at Promise.eval (eval at (/krypton/experimental/node_modules/bluebird/js/main/join.js:13:16), :6:20)
at Promise._settlePromiseAt (/krypton/experimental/node_modules/bluebird/js/main/promise.js:579:21)
at Promise._settlePromises (/krypton/experimental/node_modules/bluebird/js/main/promise.js:697:14)
at Async._drainQueue (/krypton/experimental/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (/krypton/experimental/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues (/krypton/experimental/node_modules/bluebird/js/main/async.js:15:14)
at runCallback (timers.js:570:20)
at tryOnImmediate (timers.js:550:5)
at processImmediate [as _immediateCallback] (timers.js:529:5)
390
Update interactions for selecting a table to match new design
Brett Hobbs
Need links to Dave’s design
391
Add hasAdminPermissions for bitbucket
we should also rename hasAdminPermissions to canRegisterWebhooks
392
fetchGitHubData workflow is failing because of 404's from GitHub api
Brett Hobbs
393
Carry over items not showing in new JIRA sprint
Oleg Vaskevich
Items we carried over from the last sprint are not appearing in the new sprint.
See the JIRA integration in KrPD or Dev Ops Dash
394
Swallowed error while trying to connect JIRA... left user hanging as to what was happening.
Brett Hobbs
395
BitBucket webhook registration is failing for Matt's doc
Brett Hobbs
396
We should hide "Scenario" from the datasources list
Nigel Ellis
Talked w/ Lane and Jason on the recruiting team – they still want it as an experiment. So let’s pull it out of the datasources experiment and put it in its own… (doing gardening for that team, I know – but it’s impacting our users)
397
Column names changing over and over again adding and removing '(Disabled)'
Oleg Vaskevich
398
High5 github fetches are all failing
Brett Hobbs
399
Formula Autocomplete does not work for items starting with a number or symbol
Nigel Ellis
401
No repos show up for Swift.ly after connecting to BitBucket
Nigel Ellis
402
Have section list default to open with new docs
Rhed Shi
Was feedback from John Lilly during the board meeting – don’t know it’s there.
407
LIST_PROPERTIES() returns internal values when called on regular grid
413
Thread sync frequency, start time, and register webhooks through from the client
Brett Hobbs
These will be exposed in the new UI
414
Add filter doesn't work on BloomBoard doc
Rhed Shi
The filter is updated but the control never appears.
415
GoFundMe doc will not snapshot
Brett Hobbs
At this point its getting killed while applying a single op:
All 5 Jira projects pushing into it are paused.
423
Bitbucket Icon
Dave Wright
426
Keep payload status up to date while processing it
Oleg Vaskevich
Right now the column defaults to new but never gets updated
428
WebHooks Upgrades
Oleg Vaskevich
We’re running into production issues with webhooks and we need to fix those and add polish
429
Investigate BitBucket integration
Nigel Ellis
Eval suitable client
Compare to existing Github client
434
Parsing of custom fields should be tolerant to nested = and ,
Nigel Ellis
Followup from KPD-165 which built a jenky parser for pulling out custom field values.
438
data sink settings are too large for index
Oleg Vaskevich
Error: index row size 2736 exceeds maximum 2712 for index “data_sinks_type_doc_id_config_data_key”
at PostgresQueryHelper._query (/krypton/experimental/modules/server/database/src/postgres_query_helper.js:18:34)
at PostgresQueryHelper.nonQuery (/krypton/experimental/modules/server/database/src/postgres_query_helper.js:43:17)
at DatasourcesStoragePostgres.updateDataSinkConfigData (/krypton/experimental/modules/server/datasources/src/datasources_storage_postgres.js:424:30)
at DatasourcesStorage.updateDataSinkConfigData (/krypton/experimental/modules/server/datasources/src/datasources_storage.js:77:41)
at jiraHelpers.reconcileAndGetIssuesCustomFieldsMapping.tap.issuesCustomFields (/krypton/experimental/modules/server/workflows/src/push_jira_data.js:59:63)
at Object.tapHandler (/krypton/experimental/node_modules/bluebird/js/main/finally.js:64:23)
at Object. (/krypton/experimental/node_modules/continuation-local-storage/context.js:76:17)
at Object.tryCatcher (/krypton/experimental/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (/krypton/experimental/node_modules/bluebird/js/main/promise.js:507:31)
at Promise._settlePromiseAt (/krypton/experimental/node_modules/bluebird/js/main/promise.js:581:18)
at Promise._settlePromises (/krypton/experimental/node_modules/bluebird/js/main/promise.js:697:14)
at Async._drainQueue (/krypton/experimental/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (/krypton/experimental/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues (/krypton/experimental/node_modules/bluebird/js/main/async.js:15:14)
at runCallback (timers.js:570:20)
at tryOnImmediate (timers.js:550:5)
439
Parsing sprint, epic, story points
Nigel Ellis
442
Add column entry point for adding slicers in Canvas
Nigel Ellis
Re-enable slicer scenarios using new multi-select controls on Canvas.
443
Double click on multiselect option selects option above
Nigel Ellis
444
Very few prs have synced from BloomBoard-Research/bb-core-app
Brett Hobbs
Tim thinks the most active repo for his team is bb-core-app and yet we only pulled in 35 prs to begin with.
445
JIRA schema should include these fields: Labels, Fix versions, Watch Count & Description
Brett Hobbs
446
Create entrypoint for adding a bound multi-select control to filter column values (acts as slicer)
Nigel Ellis
448
Remove legacy Slicer controls
Remove support for legacy slicer controls:
This will be subsumed by multiselect controls on the canvas with a filter binding.
450
Add column entry point for setting up a slicer and throws it in the canvas above the table
Nigel Ellis
452
Support JIRA for non-admin after the application has been registered (api sync, but not webhook)
Rhed Shi
453
Pop modal when you try and connect to JIRA when Krypton has not been registered with the JIRA instance
Rhed Shi
456
Support github for non admins
Rhed Shi
Pass a flag to the configure workflow
Skip the webhook set up when they aren’t and admin (still create an endpoint, just don’t register it)
Lower the periodic sync to 1 hour?
458
Investigate duplicate key failure in github push data workflow
Rhed Shi
One outstanding issue I’d love help with is this failing push workflow
[3:00]
Its paused now but its hitting a duplicate key issue which means we’ve got bad push data or a bug
[3:00]
It would be cool to a) figure out what’s wrong b) get some new tools to make this easier to debug in the future
461
Stop adding noop head pushes to the pushes table
Brett Hobbs
471
Selecting "show hidden" in row detail on linked-table doesn't expand and takes you to the base table
479
Remove slicers from github inflation schema
Brett Hobbs
Since we switched to composable controls these old style slicers do not function properly.
480
MULTISELECT: Unable to select final item and Exception on attempting it
Nigel Ellis
481
Control Config: right clicking on multiselect control brings up the browser context menu initially
Nigel Ellis
-Create a multselect control
Expected config panel
482
Formula not marked as broken if an undeleted control is deleted again
Christopher Eck
Note that this works for regular table. Doesn’t seem to work just for controls
Expected: Canvas formula to be broken
483
When document is shared as read-only, sliders are still draggable
Christopher Eck
Make all controls read-only in read-only doc
485
LIST_PROPERTIES does not show up in auto complete options with control experiment turned on
Christopher Eck
486
Cell-edit mode for control formatted columns should allow editing the raw value.
Christopher Eck
487
GET_PROPERTY doesn't recalc on property change
Christopher Eck
491
MULTISELECT should add scroll bars when rendering long list of items
Nigel Ellis
MultiSelect - No way to scroll through a long list of choices.
Should be a simple CSS overflow prop.
492
CARD formulas should be able to render column output formats
Nigel Ellis
If a column has an output format defined, it would be helpful if the CARD magically respected the output format when rendering the CARD. For example if the CARD has a CHECKBOX format, this could be rendered as CARD(ColumnXXX). If we can’t get this to work easily we can create a wrapping formula columnXXX.OUTPUTFORMAT().
496
Add support for easy single select on dbl click
Former user
502
Copy/pasting a control doesn't render until I refocus my selection somewhere
Christopher Eck
503
_MATCHES formula doesn't work with Canvas MULTISELECT control
Nigel Ellis
505
Merge "Enable turning on lightbox for image formulas" into the product
Brett Hobbs
E.g. turn on for everyone
507
Delete a column of controls throws RTE
Nigel Ellis
508
Protect control config editing from bad formulas
Nigel Ellis
509
We don't carry the control type through copy/paste
Christopher Eck
510
Prototype list / card views using Grids
Nigel Ellis
Fast and dirty prototype to trail grid views as lists.
511
MULTISELECT controls for Canvas and formulas
Nigel Ellis
513
Characterize buggy focus behavior of modal
David Greenspan
Collect example and get a handle on the scope of buggy behavior.
Worst example is: Enter the modal by clicking on the pop-out icon, exit it using the escape key. You get into a state where it looks like the whole table is selected; clicking on table cells opens the modal; and there are errors in the console.
Also, sometimes while the modal is up, arrow keys will scroll the page behind the modal, or you find yourself typing in a cell.
520
Add style option to IMAGE formula: IMAGE(url, width, height, name, style). Start with 'circle' to create circular images
Nigel Ellis
522
Formula results of bool don't work properly with the slicer
Brett Hobbs
525
Row URLs should update w/ popped modal
Rhed Shi
Perhaps something like:
526
Modal entry point adjustments
David Greenspan
Entry point adjustments
Increase the space between left edge of table and right edge of row ID numbers. It is currently 10px but should be closer to 18px.
When visible, increase the space between the right edge of the “open” icon and the left edge of the row grabber. Currently, it is 4px but should be 10px.
Here is a screenshot showing the staged version vs. the desired placement from the figma:
The hit area of “open” icon hover should extend vertically to match the height of the row. This way, when hovering over the rows vertically, the hovers will be triggered continuously without interruption. As staged, this works well when the rows are short, but as the rows increase in height, the fluidity of the hover gets choppy as the icons are shown only when the mouse hovers on the middle of the row. An example is here:
For reference, here is the original figma:
527
Selection/focus should only be in the modal
Rhed Shi
Right now we allow you to arrow around and change the selected row underneath, but we don’t really have the visual affordance to allow this.
So to start simple, you should only be in the modal. Arrow moves you around in a field you’re selected in. Tab moves between fields.
Your first focus on popping the modal should be nothing (or hidden) with the first tab dropping you into the first field. (Placing it in the first field will show the autocomplete… which is kind of unfortunate). Happy to discuss this too and hear alternatives – seemed like the best of a few crummy options.
528
Escape should close the modal, but keep the selection on the row
Rhed Shi
Today it deselects to the table:
529
For long content, modal should scroll
David Greenspan
Dave drew it up here:
Also attached for reference
530
Include activity, comments, and attachments from row inspector
Rhed Shi
Should drop them in at the bottom. For now just copy over, but we’ll do a 2nd pass after this is in.
531
Update row modal width and layout to spec
Rhed Shi
Main change is to set it to 580 px fixed width (for now). The rest of the layout properties should be the same from the current inspector (the label’s width being the width of the max element, up to some max, etc.).
532
Keyboard shortcut: open on spacebar
Rhed Shi
Open row-modal on when whole row is selected w/ the spacebar.
534
Add formula to get control metdata
Christopher Eck
Something like _GET_CONTROL_VALUE(@controlRef, fieldName)
Interesting metadata fields include things like value, type, min, max, etc.
536
Add data-bound controls in formula language
Christopher Eck
For example, =SLIDER(@valueCellRef, 1, 100)
537
Clean-up or subclass ControlGrid for controls
Christopher Eck
Each ControlGrid will consist of a Value column and Renderer column (ideally the latter is a system column).
551
Add support for default value formulas
Nigel Ellis
Currently column defaults can be specified as constants. Goal here is to expand support for formulas:
571
GitHub connected tables stay in sync in document and properly invalidate dependencies on changes
577
Tim should be able to view the contents of a row in a modal row-detail and make edits from there per the mocks in
600
Google not indexing subdomain.
zac ooi
Need immediate assistance. Google isn’t indexing any of the pages on our subdomain.
617
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Brett Hobbs
618
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Brett Hobbs
619
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Brett Hobbs
620
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Brett Hobbs
621
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Brett Hobbs
622
Issues like this one that are marked as fixed in a released version do not show up in Work mode but are included in the reports
Brett Hobbs
623
Instructions for deleting this sample board and project are in the description for this issue >> Click the "ITD-10" link and read the description tab of the detail view for more
Brett Hobbs
To delete this Sample Project (must be performed by a user with Administration rights)
To delete the Sample Project workflow and workflow scheme (must be performed by a user with Administration rights)
To delete this Board (must be performed by the owner of this Board or an Administrator)
624
As teams develop with Kanban they get better at reducing average resolution time (aka Cycle time). The Control Chart in the Reports shows this information
Brett Hobbs
625
Filters at the top of the board allow you to quickly cut down the shown items >> Try clicking the "Recently Updated" to hide work items not updated in the past day
Brett Hobbs
Creating Quick Filters
You can add your own Quick Filters in the board configuration (select Board > Configure)
626
... so 2 work items violate the limit and cause the column to be highlighted
Brett Hobbs
Setting Constraints
You can set limits (constraints) for columns on this board by editing the board’s configuration (select Board > Configure)
628
Work items flow through different stages from left to right >> Try dragging this card to "Selected for Development"
Brett Hobbs
Creating Columns
You can also add columns to this board by editing its configuration (select Board > Configure)
629
Work items are ranked in priority order (from top to bottom) >> Try dragging this card over the card below to rank its priority lower
Brett Hobbs
630
Add work items with "+ Create Issue" at the top right of the screen >> Try adding a new card now
Brett Hobbs
Creating Issues
When you click “+ Create Issue” you will be asked for the correct project (select “Integration Test Data”).
631
Kanban boards are often divided into streams of work, aka Swimlanes. By default, Kanban boards include an "Expedite" swimlane for items marked with the highest priority (like this one)
Brett Hobbs
Creating Swimlanes
You can create your own Swimlanes for this board by editing its configuration (select Board > Configure)
632
Kanban cards represent work items >> Click the "ITD-1" link at the top of this card to show the Detail view - there's more on Kanban in the 'Description' section
Brett Hobbs
About Kanban
is part of the Toyota Lean Manufacturing methodology but was popularised for use in IT by David Anderson. Broadly speaking it aims to optimize outcomes by:
To close this view of this task (called the Detail view), click the cross in the top right corner
There are no rows in this table
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.