idproject
int64 7.76k
28.8M
| issuekey
int64 675k
128M
| created
stringlengths 19
32
| title
stringlengths 4
226
| description
stringlengths 2
154k
⌀ | storypoints
float64 0
300
⌀ |
|---|---|---|---|---|---|
10,152,778 | 122,958,993 | 2023-02-02 17:48:09.933 | Boost transactions display wrong text in the Wallet | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Boost transactions in the wallet appear as Boost offers to `@mindsboost`.
### Steps to reproduce
Case 1:
- Create a Boost in V3
Case 2:
- Reject the Boost
### Platform information
MacOS + Chrome
### What is the current *bug* behavior?
- Transactions appear in the wallet
- The transactions appear as
`Off-Chain Boost Offer to @mindsboost`
`Off-Chain Boost Offer from @mindsboost`
### What is the expected *correct* behavior?
- Transactions appear in the wallet
- The transactions appear as
`Off-Chain Boosted Content`
### Relevant logs and/or screenshots
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem) | 2 |
10,152,778 | 122,958,542 | 2023-02-02 17:37:50.300 | Email & Push notifications link to Boost console with selected post | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
Give users the best context when tapping CTAs on emails and push notifications.
## What needs to be done
When tapping a CTA on a Boost-related email and/or push notification, we should navigate the user to the Boost console with the relevant post displayed exclusively (e.g. how Supermind emails work).
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [x] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] Introduce new single view page
- [ ] Notifications and emails to link to the single page
- [ ] Ensure the ACL is restricted to only the boost owner
- [ ] Designs to mirror supermind single page
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 5 |
10,152,778 | 122,953,938 | 2023-02-02 16:08:30.796 | Move Blocklists to Vitess and integrate with boost feeds | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
Don't show users content from channels they've blocked.
## What needs to be done
- Give User A has blocked Channel Y,
- and Channel Y creates a Boost,
- when User A views Boosts,
- then Channel Y's Boosts are not served.
### Schemas
TBD (user_blocklist)
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [ ] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] Migrate Block table from Cassandra -> Vitess
- [ ] Boost query should join against new Vitess block list
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 5 |
10,152,778 | 122,857,456 | 2023-02-01 16:22:00.586 | Duplicate emails being sent - investigate & fix | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Reports of duplicate emails being sent or no emails being sent.
### Steps to reproduce
Unknown as of yet - need to triage.
### Platform information
Platform web
### What is the current *bug* behavior?
Reports of dupe emails and emails not coming through
### What is the expected *correct* behavior?
Emails should come through and not be duplicated
### Relevant logs and/or screenshots
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem) | 3 |
10,152,778 | 122,796,568 | 2023-01-31 21:53:10.316 | Preserve UTM codes in link previews | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
Enable marketers to measure the impact of posting on Minds / Boosting on Minds.
## What needs to be done
When an activity post contains a link with UTM parameters, and a link preview is added to the post, then the link preview should maintain the UTM parameters.
Currently, UTM parameters are preserved if the user clicks the URL address in the post, but not if the user clicks the link preview.
Example post: https://www.minds.com/newsfeed/1467274467364311058
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [x] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] Ensure we use the raw link instead of the canonical url
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 1 |
10,152,778 | 122,697,124 | 2023-01-30 17:12:27.130 | Custom fields for Mautic segmenting | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
Enable more focused communications w/ Minds community through Mautic.
## What needs to be done
Add attributes to contacts that enable creating Mautic segments.
| Custom field | Goal | Done |
|-----------------------------------------|------------------------------------------------|------|
| KITE segment | Engagement, Minds+ subscriptions, Resurrection | [x] |
| Last Boosted: Cash | Boost buys, Research | [x] |
| Last Boosted: Token | Boost buys | [x] |
| Last posted | Engagement, Boost buys | [x] |
| Token balance | Minds+ subscriptions | [x] |
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [ ] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] ...
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 5 |
10,152,778 | 122,693,579 | 2023-01-30 16:11:53.888 | Boost text updates (mobile) | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
<!---
Clearly outline the goal of the issue and why we are doing it
--->
Simplify bottom bar text on boost.
## What needs to be done
<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
[Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=863%3A19887&t=W4VuvJ1FXi8LTFLu-1)
**Web**
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [x] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] ...
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 3 |
10,152,778 | 122,669,977 | 2023-01-30 12:02:39.608 | Holding rewards show as zero in wallet | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Holding rewards show as zero in wallet
### Steps to reproduce
1. Have some on-chain tokens
1. Look into your wallet
### Platform information
Brave, Win10
### What is the current *bug* behavior?
Wallet shows zero in holding section
### What is the expected *correct* behavior?
Wallet should show proper amount in holding section
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
### UX Design
[Figma](https://www.figma.com/file/tBOvE8yIILW49vECySCLpZ/Earnings?node-id=163%3A2911&t=lKTi6szGDxu4oxNk-1)
**Web**
**Mobile**
 | 1 |
10,152,778 | 122,658,531 | 2023-01-30 09:12:49.975 | "Access denied" when posting bitchute links | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
"Access denied" when posting bitchute links:
### Steps to reproduce
1. Post a link to bitchute video
2. See it has access denied in it
I posted 5 different link examples (one of them works) to this hashtag: https://www.minds.com/discovery/search?q=%23testbitchute&f=latest&t=all
### Platform information
Any
### What is the current *bug* behavior?
Access denied instead of preview
### What is the expected *correct* behavior?
Should see the preview
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem) | 0 |
10,152,778 | 122,504,408 | 2023-01-26 18:10:35.844 | Controversial Boost doesn't appear in new Boost Console | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
I've made a few test Boosts in V3 on Staging. One Boost is not appearing in my Boost Console.
The Boost is of this activity: https://www.minds.com/newsfeed/1458689744366997519
I targeted the `Controversial` audience, with a 1 token boost for 1 day.
Differences between this and Boosts that did show up in my Boosts Console:
- Different activities were Boosted
- This one targeted `Controversial` while others targeted `Safe`
### Steps to reproduce
- Boost this post: https://www.minds.com/newsfeed/1458689744366997519
- Target the `Controversial` audience
- Boost for 1 token over 1 day
### Platform information
- MacOS + Chrome
### What is the current *bug* behavior?
- The Boost does not appear in the Boost Console
### What is the expected *correct* behavior?
- The Boost does appear in the Boost Console, in a `pending` state
### Relevant logs and/or screenshots
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem) | 1 |
10,152,778 | 122,435,552 | 2023-01-25 15:13:09.386 | Guest mode is redirecting to /login | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Guest mode is redirecting to /login.
### Steps to reproduce
- Log out of Minds
- Navigate to minds.com
### Platform information
- MacOS + Chrome
- Windows + Brave
### What is the current *bug* behavior?
- The Guest Mode homepage loads
- Quickly after, the user is redirected to /login
### What is the expected *correct* behavior?
- The Guest Mode homepage loads
- The user is NOT redirected to /login
### Relevant logs and/or screenshots
You can view this behavior at the beginning of this user test video.
https://dashboard.userbrain.com/shared/lv26jq3l8p97
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem) | 2 |
10,152,778 | 122,392,181 | 2023-01-24 22:05:10.882 | Register form does not display warning of invalid character use | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
The register form does not a display warning when an invalid character is input to the `Username` field.
### Steps to reproduce
- Navigate to https://www.minds.com/register
- Input an invalid character in the `Username` field, e.g. `{`
### Platform information
- MacOS + Chrome
- Windows + Brave
### What is the current *bug* behavior?
- The Register modal changes size as if something changed.
- There's no warning about the invalid character.
### What is the expected *correct* behavior?
- The Register modal does NOT change size.
- There's a warning about the invalid character used.
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem) | 2 |
10,152,778 | 122,323,380 | 2023-01-23 19:49:12.548 | Add link to old Boost console in the new one | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
Enable Boost customers to navigate to the retired legacy Boost console.
## What needs to be done
- Given a customer navigates to the new v3 Boost console,
- and the customer has Boosts in the retired legacy Boost system (v2),
- when the v3 Boost console is displayed,
- then a link to v2 Boost console is presented.
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
[Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=862%3A19484&t=W4VuvJ1FXi8LTFLu-1)
**Web**
**Mobile**
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [ ] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] ...
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 2 |
10,152,778 | 122,315,430 | 2023-01-23 16:47:26.253 | Boost text updates | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
<!---
Clearly outline the goal of the issue and why we are doing it
--->
Simplify bottom bar text on boost.
## What needs to be done
<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
[Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=863%3A19887&t=W4VuvJ1FXi8LTFLu-1)
**Web**
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [x] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] ...
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 1 |
10,152,778 | 122,313,524 | 2023-01-23 16:15:59.928 | Update copy on Boost marketing page | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
Ensure the [Boost marketing page](https://www.minds.com/boost) copy reflects the way the new Boost system works.
## What needs to be done
Copy changes [are outlined here](https://docs.google.com/document/d/10lJko0_tpvu0Wxwv-AqTmPBRracS0dLdc5fVuhjc8eI/edit#heading=h.yt10gdju391g).
- Update copy for top section, `Expand your reach and gain thousands of views`
- Update copy for the 2nd section, `1 token = 1,000 views`
- Update copy for the 3rd section, `Boost Campaigns`
- Remove the 4th section, `Boost Offers`
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [ ] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] ...
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 1 |
10,152,778 | 122,313,057 | 2023-01-23 16:07:25.540 | Create an in-feed notice promoting Boost Partners | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
<!---
Clearly outline the goal of the issue and why we are doing it
--->
Clearly communicate to users of Boost Partners through the use of an in-feed notice that prompts them to join Boost Partners.
## What needs to be done
Create an in-feed notice for Boost Partners.
Read more links to: https://www.minds.com/info/blog/introducing-boost-partners-program-1477787849246904328
Settings links to Boost settings.
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
[Figma ](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=846%3A19064&t=6dPYn7qWCP7cjdH8-1)
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] ...
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 2 |
10,152,778 | 122,311,101 | 2023-01-23 15:43:24.092 | Update copy on Monetize modal | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
- Better communicate the existing content policy on Premium Content
- Communicate that the existing policy will be enforced
## What needs to be done
Update the copy on this modal:
> Submit this post to Minds+ Premium Content and earn a share of our revenue based on how it performs.
> [ ] I agree to the [https://www.minds.com/p/monetization-terms](Minds monetization terms) and have the rights to monetize this content.
>
> - This content is my original content
> - This content is exclusive to Minds+
>
> I understand that violation of these requirements may result in losing the ability to publish Premium Content for Minds+ members.
Old:
New:
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [x] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] The text has been changed
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 1 |
10,152,778 | 122,206,991 | 2023-01-20 18:24:38.065 | Update Boost Settings UI to introduce new setting options | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
- Add value to Minds+ subscription prop
- Give Minds+ customers more control of their content
- Give content owners more control over how their content is presented
- Enable eligible customers to earn more from Boost partners by enabling more lucrative audience targeting
## What needs to be done
Enable Minds+/Pro subscribers to disable Boosts on their content, including channel pages, SEPs, etc.
Bonus if the control is exposed to non-subscribers and used as a point of converting to a Minds+ subscriber.
Give all users an option to enable/disable Controversial Boosts from appearing on pages they own (channel pages, SEPs, etc.).
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
**Web**
See [Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=874%3A19959&t=BaObSlJNAm1veHmY-1) for hover states on tooltips and tooltip copy
**Default View For Non-Minds+ User**
**Default View For Minds+ User**
**Serve Boosts on my channel tooltip**
**Mobile**
See [Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=874%3A19959&t=BaObSlJNAm1veHmY-1) for hover states on tooltips and tooltip copy
**Default View For Non-Minds+ User**
**Default View For Minds+ User**
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [x] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] ...
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 5 |
10,152,778 | 122,202,890 | 2023-01-20 16:56:03.043 | Remove Boost from Admin queue after it's approved or rejected | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
Increase efficiency for the Admin team inside of the new Boost queue.
## What needs to be done
- Given a Boost appears in the Admin queue,
- when an Admin either approves or rejects the Boost,
- then the Boost is visually removed from the Admin queue
Note that the goal here is Admin efficiency. The faster we can get adjudicated Boosts out of the queue, the faster they can get through it.
With this in mind, worth considering prioritizing removing an item visually quickly, without waiting for network / validation. On the rare occasion that network / validations occurs, it may be preferable to quickly dismiss that item and have it re-appear in the queue (flash), rather than keep the item in the queue for the duration of the network / validation request.
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
## Mobile
<!---
Does a mobile card need to be created? Any notes for mobile?
--->
- [ ] Is Mobile Required?
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] After a boost is actioned, it should be removed from the page.
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 2 |
10,152,778 | 122,149,335 | 2023-01-19 22:34:07.093 | Communicate upcoming Boost changes to Boosters | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
- Inform current Boosters about the upcoming changes to Boost
- And that the switchover may impact the Boost they are about to create
## What needs to be done
Add some messaging to the current Boost modal that communicates that (a) things are changing soon, and that (b) their Boost delivery may different than expected because of it.
Link copy points to: https://www.minds.com/info/blog/bid-farewell-the-boost-backlog-1445548466339057665
Given we will likely have a sizable Boost backlog of v2 Boosts when we're ready to switch to v3, @benhayward.ben proposed migrating v2 Boosts to v3 system. The user impact is that their Boosts will effectively be moved to the bidding system, in which their view numbers are not guaranteed. Customers should be aware of this possibility with their newly-purchased v2 Boosts.
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
[Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=879%3A20716&t=BaObSlJNAm1veHmY-1)
**Web**
**Mobile**
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] ...
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 2 |
10,152,778 | 121,764,534 | 2023-01-13 19:21:15.044 | Add Boost-related context to 'action' events and views | <!---
Please read this!
The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->
## Goal
- As Minds, I want to know what is the engagement rate of Boosted posts in various positions in the app so that I can optimize the performance of Boosts.
- As a Boost user, I want to know what engagements on my post are attributable to a Boost, so that I can evaluate the ROI for Boosting.
## What needs to be done
Add context to engagement events (upvotes, downvotes, reminds, comments) that enables us to discern these engagements from organic appearances and Boosted appearances.
The 'view' event currently has support for supplying client_meta which includes the campaigns, medium etc. We should extend these to be sent along with actions such as upvotes etc.
For snowplow we should consider introducing a new `context` that will store the above information. The new context should also be able to provide the context of the feed, such as recommendation slot.
## QA
<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
## UX/Design
<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
## Mobile
- [x] Mobile ticket required?
Mobile will need to send the context with the events such as 'votes'.
## Personas
<!---
Who does this user impact and why (optional)
--->
## Experiments
<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] Action events should include the context of the entity
- [ ] Backend should use the context when emitting out to snowplow
- [ ] Update 'view' events to also use the new context
## Definition of Ready Checklist
- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments | 5 |
10,171,263 | 25,326,678 | 2019-09-26 03:22:02.733 | XSRF Prevention Middleware | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 25,326,658 | 2019-09-26 03:20:48.471 | Admin Middleware | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 1 |
10,171,263 | 25,326,650 | 2019-09-26 03:20:15.836 | Logged-in Middleware (Disallow anonymous access to certain endpoints) | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 1 |
10,171,263 | 25,326,638 | 2019-09-26 03:18:55.495 | Catch unhandled exception on route map handlers. Build a response and ping Sentry | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 3 |
10,171,263 | 25,326,456 | 2019-09-26 03:16:52.086 | Allow module route maps to specify groups with common middleware (as children routes) | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 25,326,449 | 2019-09-26 03:15:40.574 | Allow module route maps to specify one or more middleware | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 25,326,433 | 2019-09-26 03:13:36.085 | Allow modules to map explicit routes handled via DI bindings | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 25,325,960 | 2019-09-26 03:09:49.488 | Move pre-PSR-7 router to it's class and create a fallback middleware | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 1 |
10,171,263 | 25,325,940 | 2019-09-26 03:07:22.912 | Request handler prototype | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 3 |
10,171,263 | 25,325,773 | 2019-09-26 02:58:16.678 | Recurring Pro subscription payments using multi-currency wire | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 3 |
10,171,263 | 25,325,725 | 2019-09-26 02:55:44.389 | Pro channels should have Plus benefits | `isPlus()` should return true if `isPro()` is true | 1 |
10,171,263 | 25,321,566 | 2019-09-25 23:22:01.024 | Error: Call to a member function isOwner() on null when trying to read deleted group's review queue | Sentry Issue: [ENGINE-4Y](https://sentry.io/organizations/minds-inc/issues/1195076403/?referrer=gitlab_integration)
```
Error: Call to a member function isOwner() on null
File "/Controllers/api/v1/groups/review.php", line 22, in Minds\Controllers\api\v1\groups\review::get
if (!$group->isOwner($user) && !$group->isModerator($user)) {
File "/Api/Factory.php", line 70, in Minds\Api\Factory::build
return $handler->$method($pages);
File "/Controllers/api/api.php", line 76, in Minds\Controllers\api\api::get
return Factory::build($pages, $this->request, $this->response);
File "/Core/Router.php", line 138, in Minds\Core\Router::route
return $handler->$method($pages);
File "/index.php", line 9
$router->route();
``` | 1 |
10,171,263 | 25,321,532 | 2019-09-25 23:15:42.348 | Error: Call to undefined function elgg_normalize_url() when building SEO image tag URL | Sentry Issue: [ENGINE-49](https://sentry.io/organizations/minds-inc/issues/1192152261/?referrer=gitlab_integration)
```
Error: Call to undefined function elgg_normalize_url()
File "/classes/ElggEntity.php", line 1005, in ElggEntity::getIconURL
return elgg_normalize_url($url);
File "/Core/Media/SEO.php", line 80, in Minds\Core\Media\SEO::viewHandler
'og:image' => $entity->getIconUrl('xlarge'),
File "[internal]", line 0, in call_user_func_array
File "/Core/SEO/Manager.php", line 69, in Minds\Core\SEO\Manager::get
$meta = call_user_func_array(self::$routes[$route], [array_reverse($slugs)]) ?: [];
File "/var/www/Minds/front/dist/en/index.php", line 2, in include
$meta = Minds\Core\SEO\Manager::get();
...
(3 additional frame(s) were not displayed)
``` | 2 |
10,171,263 | 25,321,504 | 2019-09-25 23:12:45.775 | Error: Call to a member function getEmail() on null when reading settings | Sentry Issue: [ENGINE-26](https://sentry.io/organizations/minds-inc/issues/1179022582/?referrer=gitlab_integration)
```
Error: Call to a member function getEmail() on null
File "/Controllers/api/v2/settings/emails.php", line 41, in Minds\Controllers\Api\v2\settings\emails::get
'email' => $user->getEmail(),
File "/Api/Factory.php", line 70, in Minds\Api\Factory::build
return $handler->$method($pages);
File "/Controllers/api/api.php", line 76, in Minds\Controllers\api\api::get
return Factory::build($pages, $this->request, $this->response);
File "/Core/Router.php", line 138, in Minds\Core\Router::route
return $handler->$method($pages);
File "/index.php", line 9
$router->route();
``` | 2 |
10,171,263 | 25,321,471 | 2019-09-25 23:09:05.235 | Exception: user_guid be be sent when getting Update Markers | Sentry Issue: [ENGINE-D](https://sentry.io/organizations/minds-inc/issues/1177469648/?referrer=gitlab_integration)
```
Exception: user_guid be be sent
File "/Core/Notification/UpdateMarkers/Repository.php", line 34, in Minds\Core\Notification\UpdateMarkers\Repository::getList
throw new \Exception('user_guid be be sent');
File "/Core/Notification/UpdateMarkers/Manager.php", line 28, in Minds\Core\Notification\UpdateMarkers\Manager::getList
return $this->repository->getList($opts);
File "/Core/Groups/Membership.php", line 649, in Minds\Core\Groups\Membership::getGroupsByMember
'limit' => 1000,
File "/Controllers/api/v1/groups.php", line 52, in Minds\Controllers\api\v1\groups::get
'offset' => (int) $_GET['offset'],
File "/Api/Factory.php", line 70, in Minds\Api\Factory::build
return $handler->$method($pages);
...
(3 additional frame(s) were not displayed)
```
We need to check to make sure that we check for an authenticated user before we request update markers | 3 |
10,171,263 | 25,304,162 | 2019-09-25 15:25:27.328 | (feature) replace admin check with permissions | Everywhere we check admin permissions on the backend, we need to feature flag check the new permissions flags | 2 |
10,171,263 | 25,302,105 | 2019-09-25 14:33:35.306 | (bug): Disallow /pro/channel on non-Pro channels | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 1 |
10,171,263 | 25,299,914 | 2019-09-25 13:38:12.967 | (chore): Investigate ban reasons inconsistencies. | See https://gitlab.com/minds/engine/merge_requests/328#note_221820226 | 3 |
10,171,263 | 25,249,801 | 2019-09-24 15:11:07.650 | (bug): Switch ban email to another address | Currently it tells the user to reply to no-reply. | 1 |
10,171,263 | 25,133,150 | 2019-09-23 20:02:02.326 | (bug): Ensure Contributions\Repository handles faulty $rows values | Sentry Issue: [ENGINE-J](https://sentry.io/organizations/minds-inc/issues/1177479145/?referrer=gitlab_integration)
```
Error: Call to a member function pagingStateToken() on boolean
File "/Core/Rewards/Contributions/Repository.php", line 124, in Minds\Core\Rewards\Contributions\Repository::getList
'token' => $rows->pagingStateToken()
File "/Controllers/api/v2/blockchain/contributions.php", line 36, in Minds\Controllers\api\v2\blockchain\contributions::get
'offset' => $offset
File "/Api/Factory.php", line 69, in Minds\Api\Factory::build
return $handler->$method($pages);
File "/Controllers/api/api.php", line 76, in Minds\Controllers\api\api::get
return Factory::build($pages, $this->request, $this->response);
File "/Core/Router.php", line 137, in Minds\Core\Router::route
return $handler->$method($pages);
...
(1 additional frame(s) were not displayed)
``` | 2 |
10,171,263 | 25,131,549 | 2019-09-23 19:35:03.018 | (bug): Wire\Thresholds should handle NULL users (logged-out) | Sentry Issue: [ENGINE-1T](https://sentry.io/organizations/minds-inc/issues/1178004156/?referrer=gitlab_integration)
```
Cassandra\Exception\InvalidArgumentException: num must be a long, double, numeric string or a Cassandra\Varint instance, given
File "/Core/Wire/Sums.php", line 114, in Cassandra\Varint::__construct
new \Cassandra\Varint($this->sender_guid),
File "/Core/Wire/Sums.php", line 114, in Minds\Core\Wire\Sums::getSent
new \Cassandra\Varint($this->sender_guid),
File "/Core/Wire/Thresholds.php", line 63, in Minds\Core\Wire\Thresholds::isAllowed
$amount = $sums->getSent();
File "/Core/Media/Thumbnails.php", line 26, in Minds\Core\Media\Thumbnails::get
if (!Di::_()->get('Wire\Thresholds')->isAllowed($loggedInUser, $entity)) {
File "/Controllers/fs/v1/thumbnail.php", line 36, in Minds\Controllers\fs\v1\thumbnail::get
$thumbnail = $mediaThumbnails->get($pages[0], $size);
...
(4 additional frame(s) were not displayed)
``` | 2 |
10,171,263 | 25,113,452 | 2019-09-23 12:20:01.695 | Full test plan for destkop | null | 3 |
10,171,263 | 25,097,825 | 2019-09-23 02:26:56.326 | (feat): Implement referral system to Pro Domain | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 25,090,455 | 2019-09-22 16:58:11.425 | (bug): videos not playing when webtorrent enabled | It seems that reminded videos do not render a working "play" button. Multiple users have reported this, but I've not been able to replicate.
* https://www.minds.com/newsfeed/1022536967470239744 <br>
* https://www.minds.com/newsfeed/1022434607589212160 <br>
* https://www.minds.com/newsfeed/1022400200341803008 <br>
* https://www.minds.com/newsfeed/1022045056894849024 <br>
* https://www.minds.com/newsfeed/1022855418898337792 <br>
* https://www.minds.com/newsfeed/1022863137753997312 <br> | 3 |
10,171,263 | 25,048,836 | 2019-09-20 15:39:22.241 | (feat): Turn on feature flags when staging cookie present. | Clients should be able to set `staging-features=<base64_encoded_JSON>` along with `staging=1`
Base64 Encoded JSON, when decoded, should have the following structure:
```JSON
{ "pro": true, "es-feeds": true }
```
That cookie should affect the outcome of `Features\Manager::has()` and `Features::Manager::export()` | 2 |
10,171,263 | 25,044,245 | 2019-09-20 13:04:20.417 | (chore): Follow-up from "(feat): Minds Pro" | The following discussions from !308 should be addressed:
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_218633043):
> This is using legacy JWT library. We should be using the new JWT library used by Core/Sessions/Manager, Core/Security/SignedUri.php etc. The new one is the `Lcobucci\JWT` library
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219735047):
> Please remove this block. This should be for registration only and also not at the controller level. The `from` parameter is also not very clear and potentially insecure.
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219735624):
> This should be done via the referral cookie. Please remove from the controllers.
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219735826):
> Why is this added in here?
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219738230):
> remove from here. There is already referral logic.
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219738679):
> This should be set in the constructor
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219738923):
> Why is this no longer set?
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219739965):
> and here?
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219740651):
> This should be injected
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219741300):
> return type `:void`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744604):
> return type `: Jwt`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744606):
> return type `: array`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744607):
> return type `: string`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744608):
> return type `: string`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744610):
> return type `: array`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744611):
> return type `: Manager`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744612):
> return type `: array`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744613):
> return type `: HydrateSettingsDelegate`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744614):
> return type `: InitializeSettingsDelegate`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744615):
> docs and return type needed
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744616):
> return type `: ?Settings`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744618):
> return type `: string`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744619):
> return type `: string`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744622):
> return type `: void`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744624):
> return type `: string`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744625):
> return type `: Manager`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744627):
> return type `: Manager`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744629):
> return type `: bool`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744633):
> return type `: bool`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744635):
> return type `: bool`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744636):
> return type `: ?Settings`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744637):
> return type `: bool`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744639):
> return type `: Response`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744641):
> return types needed for this file
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744643):
> return type `: string`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744645):
> return type `: array`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744647):
> return type `: array`
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744648):
> Return types needed for this file
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744650):
> return types needed
- [x] @markeharding started a [discussion](https://gitlab.com/minds/engine/merge_requests/308#note_219744657):
> return types | 2 |
10,171,263 | 24,993,236 | 2019-09-19 14:39:02.961 | (fix): hashtag filters do not detect hashtags from posts with only text or outside links | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,985,364 | 2019-09-19 11:30:24.872 | Kite user guid is not logged properly | In Kite index some documents has short guid:
```
9126
36989
928292
87334836935
7623355377579362
21891019491592981
27667508119009771
29759722821258901
34209858267472015
37859586873321869
43862099460765620
47580495288740679
48383866281168139
50759326361202941
56403706515584002
58443165904275271
65681389729650860
78757476555697447
82352297385550137
83696497744413492
90167915953349636
91260549480632321
95117807210039571
``` | 2 |
10,171,263 | 24,962,728 | 2019-09-18 20:29:44.583 | Docker structure for new frontend server | - [ ] Replace front-init container with a front-server
- [ ] Hot reload in dev mode? | 2 |
10,171,263 | 24,962,337 | 2019-09-18 20:13:00.754 | Refactor SEO from backend to frontend | Currently the SEO is handled by the backend. Moving to the frontend, once SSR is established (https://gitlab.com/minds/front/issues/1930) will lead to a unified environment with a single place for pages to be handled. | 5 |
10,171,263 | 24,959,070 | 2019-09-18 18:18:30.568 | (refactor): Use newest library for JWT token | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,956,222 | 2019-09-18 16:22:05.571 | (bug): block does not work in groups | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
If user A blocks user B, user B will still appear in the group-feed of user A.
### Steps to reproduce
Unknown - it appears to happen rarely, but very randomly.
I have seen multiple reports and I and other team members have seen it happen first-hand.
### Platform information
Cross-platform web.
### What is the current *bug* behavior?
Blocked users show up in feeds.
### What is the expected *correct* behavior?
Blocked users should not appear for the blocker.
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
/label ~"T \- Bug" ~"S \- Triage:new"
Let's make sure
- [x] Banned users disappear from the UI on feeds
- [x] Banned users do not appear on reload
- [x] We need to make sure that admins can only see blocked users by explicitly going to their channel page. They should not be showing up in anyone's feeds. | 4 |
10,171,263 | 24,955,442 | 2019-09-18 16:10:51.165 | Framework Performance Optimisations | * Autoloader and some of the Events registration callbacks are suboptimal
* Adds properly configured opcache for dev env | 2 |
10,171,263 | 24,945,088 | 2019-09-18 13:19:07.034 | (bug): Not auto-subbing when registering | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,945,060 | 2019-09-18 13:18:33.166 | (bug): 500 when auto-subbing on login | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,936,218 | 2019-09-18 10:56:28.934 | Issue referral cookie on channel and asset pages if not already set | null | 1 |
10,171,263 | 24,932,410 | 2019-09-18 09:05:27.592 | Test User State Functionality in Review Sites | The following need tested:
* Analytics cli run daily records correct user states and sends notifications when user state changes
* Analytics cli 'incremental' run tracks user state changes for the current day and sends notification if there is going to be a user state decline
The review site will need a number of users for this that can generate activities and be registered to receive token rewards (currently not working, assuming Twilio key is needed in config).
This will need to take place over a number of days unless there is an easy way of injecting fake user activity into the backend - Reliable way would be writing a cli to do this??? | 6 |
10,171,263 | 24,922,097 | 2019-09-17 23:05:02.194 | (test): Engine spec tests | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,918,570 | 2019-09-17 20:28:16.759 | Unable to fully cancel out of video upload | chrome on apple desktop | 2 |
10,171,263 | 24,909,406 | 2019-09-17 16:46:30.687 | (fix): issues when saving settings | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 1 |
10,171,263 | 24,849,977 | 2019-09-16 19:50:20.917 | (feat): Configure Traefik frontends when saving Pro settings | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 3 |
10,171,263 | 24,842,948 | 2019-09-16 16:34:03.181 | Case sensitivity on hashtags | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Case sensitivity on hashtags is detrimental to the users experience.
### Steps to reproduce
Compare the following two links and note the hashtag params difference in case.
* https://www.minds.com/newsfeed/global/top;hashtag=unfucktheworld;period=24h
* https://www.minds.com/newsfeed/global/top;hashtag=UnfuckTheWorld;period=24h
### Platform information
Cross-platform web.
### What is the current *bug* behavior?
examples, #FOObar and #fooBAR are not showing the same hashtags.
### What is the expected *correct* behavior?
Case sensitivity shouldn't make a difference for hashtags.
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem) | 2 |
10,171,263 | 24,765,631 | 2019-09-13 13:51:39.600 | (feat): Endpoint returning both Pro channel and current user | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,740,805 | 2019-09-12 20:33:36.754 | (chore): Disallow Pro self-enable | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 1 |
10,171,263 | 24,740,780 | 2019-09-12 20:32:12.403 | (feat): Allow admins to toggle Pro on channels | null | 2 |
10,171,263 | 24,740,714 | 2019-09-12 20:28:17.293 | (feat): Add validations to Settings submissions | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,733,288 | 2019-09-12 14:35:13.823 | Wire emails use the @symbol but shows the display name, not username | null | 1 |
10,171,263 | 24,700,470 | 2019-09-11 17:44:07.273 | (feat): Allow admins to submit <head> code for Pro Domain pages | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,699,621 | 2019-09-11 17:20:37.848 | (feat): Allow admins to edit Pro settings | null | 2 |
10,171,263 | 24,681,496 | 2019-09-11 11:26:18.428 | Efficient querying of views table | - [ ] Copy to elasticsearch with hourly resolution
```json
{
"resolution": "day",
"@timestamp": 1568627843000,
"entity_urn": "urn:activity:123",
"owner_guid": "456",
"views": 201
}
```
- [ ] Cli script to run over views and update hourly and update the aggregated number
- [ ] Forward plan reducing resolution on main `views` table | 3 |
10,171,263 | 24,681,364 | 2019-09-11 11:23:03.017 | Record owner_guid on views table | | Column | Type |
| ------ | ------ |
| owner_guid | bigint | | 1 |
10,171,263 | 24,678,870 | 2019-09-11 10:05:16.103 | Opt-in endpoint to join partner program | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,663,007 | 2019-09-10 22:20:21.126 | Unread messages should automatically go to top of messenger list | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Unread messages need to be displayed at the top of a user's messenger list so that they can easily find it and read it. Otherwise, the notification remains and it is confusing unless you scroll way down the list to find the unread message.
all platforms
### Relevant logs and/or screenshots
This video depicts the confusion it can cause. The video does not show this, but the reason the message marker remains there is because there was an unread message buried down the list.
 | 2 |
10,171,263 | 24,661,025 | 2019-09-10 21:08:21.892 | (fix): if editing, time_created should only be changed if it's different from entity time_created | null | 1 |
10,171,263 | 24,634,404 | 2019-09-10 10:31:00.397 | (feat) Cli controller for triggering notifications | I'm finding testing notifications a chore so wrote a cli for quickly triggering notifications for quickly testing frontend and mobile changes. | 2 |
10,171,263 | 24,612,942 | 2019-09-09 20:11:15.545 | (chore) Remove static composer hash from setup script | Instructions at https://getcomposer.org/doc/faqs/how-to-install-composer-programmatically.md
...indicate to wget the hash down eliminating the need for the hash to be static in the script | 1 |
10,171,263 | 24,603,639 | 2019-09-09 15:38:23.594 | Users not receiving points for jury duty | * This user did not receive any points on 9/4: https://www.minds.com/wallet/tokens/transactions;remote=nexticeage
* User FoxFox has not been credited for their last 4 Jury Duties.
* Other reports are floating around.
https://www.minds.com/newsfeed/1034493384498917376 <br>
https://www.minds.com/newsfeed/1036946661790953472 <br>
https://www.minds.com/newsfeed/1037315249617113088 | 2 |
10,171,263 | 24,601,286 | 2019-09-09 14:52:47.926 | Broken image placeholders | # Questions
- Does this replace broken images bulb?
- Which error screens should be included?
- What is the text that should go along with this?
# More details
Created this image for errors.
Previous error message:
New error message should be:  | 2 |
10,171,263 | 24,597,821 | 2019-09-09 13:43:45.718 | (chore): change filter to timestamp instead of time_created | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 1 |
10,171,263 | 24,541,585 | 2019-09-06 15:17:49.767 | (feat) Add user states to wallet overview endpoint | Return the list of all current user states + multiplier values | 2 |
10,171,263 | 24,473,177 | 2019-09-04 20:42:46.338 | Chore: Improved feature flags | Maintaining our feature flags in helm / config is turning into a fragile chore. Moving them over to clearly defined classes in php | 2 |
10,171,263 | 24,466,616 | 2019-09-04 15:50:51.639 | (bug): error produced when reporting group for any reason | Groups cannot be reported, there is an error.
:update @benhayward.ben
Request is 500ing throwing this into the nginx and php-fpm containers.
```
nginx_1 | 2019/09/12 17:07:53 [error] 6#6: *3362 FastCGI sent in stderr: "PHP message: Exception #1568308073: Cassandra\Exception\InvalidArgumentException: value must be a long, a double, a numeric string or a Cassandra\Bigint, given in /var/www/Minds/engine/Core/Reports/UserReports/Repository.php:60
nginx_1 | Stack trace:
nginx_1 | #0 /var/www/Minds/engine/Core/Reports/UserReports/Repository.php(60): Cassandra\Bigint->__construct(NULL)
nginx_1 | #1 /var/www/Minds/engine/Core/Reports/UserReports/Manager.php(96): Minds\Core\Reports\UserReports\Repository->add(Object(Minds\Core\Reports\UserReports\UserReport))
nginx_1 | #2 /var/www/Minds/engine/Controllers/api/v2/moderation/report.php(77): Minds\Core\Reports\UserReports\Manager->add(Object(Minds\Core\Reports\UserReports\UserReport))
nginx_1 | #3 /var/www/Minds/engine/Api/Factory.php(69): Minds\Controllers\api\v2\moderation\report->post(Array)
nginx_1 | #4 /var/www/Minds/engine/Controllers/api/api.php(81): Minds\Api\Factory::build(Array, Object(Zend\Diactoros\ServerRequest), Object(Zend\Diactoros\Response\JsonResponse))
nginx_1 | #5 /var/www/Minds/engine/Core/Router.php(137): Minds\Controllers\api\" while reading response header from upstream, client: 172.19.0.1, server: _, request: "POST /api/v2/moderation/report HTTP/1.1", upstream: "fastcgi://172.19.0.8:9000", host: "0.0.0.0", referrer: "http://0.0.0.0/groups/profile/1018930846406545413/feed"
elasticsearch_1 | [2019-09-12T17:08:08,994][INFO ][o.e.c.r.a.DiskThresholdMonitor] [HhjXpE-] low disk watermark [85%] exceeded on [Hh
``` | 2 |
10,171,263 | 24,461,580 | 2019-09-04 13:17:25.782 | More specs test | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,459,172 | 2019-09-04 12:13:26.007 | (bug): As owner, I cannot view scheduled posts | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,396,788 | 2019-09-02 18:58:25.215 | (feat): Use channel avatar as favicon | null | 2 |
10,171,263 | 24,299,741 | 2019-08-29 16:57:07.231 | Introduce collapsible titles in Help Desk | Currently all the choices in help desk are visible. We need to have the titles collapsible for ease of use.
 | 2 |
10,171,263 | 24,293,371 | 2019-08-29 13:59:44.722 | (feat): Add filter to EntityGuidResolverDelegate to exclude future entities when not owner | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 4 |
10,171,263 | 24,293,253 | 2019-08-29 13:57:49.702 | Exception: Entity is required - User cannot Boost old posts | <!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary:
when boosting older articles like I get: Http failure response for https://www.minds.com/api/v2/boost/prepare/795065334607159300?: 500 Internal Server Error
i still have more than 50 000 tokens even not gotting some recently
### Steps to reproduce:
goto https://www.minds.com/blog/view/795065334607159296 and try boost as user
### Browser and OS
FF under linux mint reported by: @lichtkind
### What is the current *bug* behavior?
User cannot boost older articles.
### What is the expected *correct* behavior?
User should be able to boost older articles.
### Relevant logs and/or screenshots
SENTRY
https://sentry.io/organizations/minds-inc/issues/1190687997/?project=1538020&query=boost
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
Sentry Issue: [ENGINE-3T](https://sentry.io/organizations/minds-inc/issues/1190687997/?referrer=gitlab_integration)
```
Exception: Entity is required
File "/Core/Boost/Checksum.php", line 58, in Minds\Core\Boost\Checksum::generate
throw new \Exception('Entity is required');
File "/Controllers/api/v2/boost/prepare.php", line 36, in Minds\Controllers\api\v2\boost\prepare::get
->generate();
File "/Api/Factory.php", line 69, in Minds\Api\Factory::build
return $handler->$method($pages);
File "/Controllers/api/api.php", line 76, in Minds\Controllers\api\api::get
return Factory::build($pages, $this->request, $this->response);
File "/Core/Router.php", line 137, in Minds\Core\Router::route
return $handler->$method($pages);
...
(1 additional frame(s) were not displayed)
``` | 1 |
10,171,263 | 24,219,799 | 2019-08-27 20:16:44.260 | Update report options | We should update the report options and flow to this: https://docs.google.com/spreadsheets/d/1UOenCMZlBVHd2Ypip40MFN4KYeXCj8eJEBOvMIxYeVo/edit#gid=0 | 6 |
10,171,263 | 24,102,540 | 2019-08-23 17:18:49.927 | (code review): Add PHP 7 return types to Core\Pro module methods | null | 2 |
10,171,263 | 24,102,524 | 2019-08-23 17:17:32.084 | (code review): Make Router middleware PSR-15/PSR-7 compliant | null | 3 |
10,171,263 | 24,102,484 | 2019-08-23 17:14:59.108 | (code review): Read root domain from Config on InitializeSettingsDelegate | Might need a new `settings.php` entry. | 1 |
10,171,263 | 24,102,376 | 2019-08-23 17:08:27.735 | (code review): Remove unnecesary features from v2/feeds/channel and move it to v2/pro/content | null | 2 |
10,171,263 | 24,102,323 | 2019-08-23 17:04:13.856 | (code review): Detach Api/Factory Pro domain for existing flow | null | 1 |
10,171,263 | 24,093,278 | 2019-08-23 13:48:06.990 | (fix): Adapt code as per review | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 2 |
10,171,263 | 24,064,612 | 2019-08-22 18:10:48.659 | (feat): Implement a short-lived cache with homepage categories content | null | 1 |
10,171,263 | 24,060,254 | 2019-08-22 15:43:24.008 | (chore): fixes for MVP internal demo | Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible. | 6 |
10,171,263 | 24,057,653 | 2019-08-22 15:24:20.556 | (bug): Logout should provide $session value - Error: Call to a member function getUserGuid() on null | Sentry Issue: [ENGINE-G](https://sentry.io/organizations/minds-inc/issues/1177477262/?referrer=gitlab_integration)
```
Error: Call to a member function getUserGuid() on null
File "/Core/Sessions/Repository.php", line 94, in Minds\Core\Sessions\Repository::delete
new Varint($session->getUserGuid()),
File "/Core/Sessions/Manager.php", line 239, in Minds\Core\Sessions\Manager::destroy
$this->repository->delete($this->session, $all);
File "/Controllers/api/v1/authenticate.php", line 124, in Minds\Controllers\api\v1\authenticate::delete
$sessions->destroy(false);
File "/Api/Factory.php", line 69, in Minds\Api\Factory::build
return $handler->$method($pages);
File "/Controllers/api/api.php", line 91, in Minds\Controllers\api\api::delete
return Factory::build($pages, $this->request, $this->response);
...
(2 additional frame(s) were not displayed)
``` | 2 |
10,171,263 | 24,049,926 | 2019-08-22 14:25:59.915 | ImagickException: no decode delegate for this image format `' @ error/constitute.c/ReadImage/504 | Sentry Issue: [ENGINE-T](https://sentry.io/organizations/minds-inc/issues/1177515385/?referrer=gitlab_integration)
```
ImagickException: no decode delegate for this image format `' @ error/constitute.c/ReadImage/504
File "/Core/Media/Imagick/Manager.php", line 60, in Imagick::__construct
$this->image = new \Imagick($value);
File "/Core/Media/Imagick/Manager.php", line 60, in Minds\Core\Media\Imagick\Manager::setImage
$this->image = new \Imagick($value);
File "/Controllers/api/v1/blog.php", line 330, in Minds\Controllers\api\v1\blog::post
$manager->setImage($_FILES['file']['tmp_name'])
File "/Api/Factory.php", line 69, in Minds\Api\Factory::build
return $handler->$method($pages);
File "/Controllers/api/api.php", line 81, in Minds\Controllers\api\api::post
return Factory::build($pages, $this->request, $this->response);
...
(2 additional frame(s) were not displayed)
```
~"Type::Bug" | 5 |
Subsets and Splits