Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

User can open own profile from system messages or from group info #7197

Closed
churik opened this issue Dec 28, 2018 · 54 comments
Closed

User can open own profile from system messages or from group info #7197

churik opened this issue Dec 28, 2018 · 54 comments
Assignees
@StatusSceptre
Labels
group-chat

Comments

@churik
Copy link
Member

churik commented Dec 28, 2018 •
edited by 0xc1c4da
Loading

Description

Type: Bug

Summary: after user has been made admin he can open own profile from group info screen

Expected behavior

user can't open own profile screen from group Group info

Actual behavior

can see own profile with options, that cannot be performed
ownpre

Reproduction

Scenario 1 (for group info):

  • Open Status on (device A, user A)
  • Create a group chat (device A, user A) with user B
  • Make User B admin
  • Log in to Status (device B, user B)
  • Open group chat with user A
  • Tap on ... > Group info
  • Tap on ... > Open Profile on your avatar

Scenario 2 (for system messages):

  • Open Status on (device A, user A)
  • Create a group chat (device A, user A) with user B
  • Tap on own avatar on message *user A* created a group.

Additional Information
@churik churik changed the title User can open own profile from group info, if he has been made admin User can open own profile from system messages or from group info, if he has been made admin Jan 25, 2019
@churik
Copy link
Member Author

churik commented Jan 25, 2019

@cammellos look at this one when you have a time.

@churik churik changed the title User can open own profile from system messages or from group info, if he has been made admin User can open own profile from system messages or from group info Feb 25, 2019
@annadanchenko annadanchenko self-assigned this May 22, 2019
@churik
Copy link
Member Author

churik commented Aug 13, 2019

cc @rachelhamlin
I'm not sure that it is required, but anyway, user can try to block yourself, I don't think it is desirable.

@rachelhamlin
Copy link
Contributor

rachelhamlin commented Aug 14, 2019 •
edited
Loading

Easier to disable, agreed! Probably an xs bounty.

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 50.0 DAI (50.0 USD @ $1.0/DAI) attached to it.

@gitcoinbot
Copy link

💰 A crowdfund contribution worth 0.01000 DAI (0.01 USD @ $1.0/DAI) has been attached to this funded issue from @intan167.💰

Want to chip in also? Add your own contribution here.

@annadanchenko annadanchenko removed their assignment Aug 30, 2019
@rachelhamlin
Copy link
Contributor

@speedyFixer are you still interested and available to work on this issue? Just assigned you! Apologies for delay.

@speedyFixer
Copy link
Contributor

Hi @rachelhamlin , I'm traveling, I will go back on Saturday, so I will can tackle all of this on Sunday. Is It OK?

@rachelhamlin
Copy link
Contributor

@speedyFixer sure! I'll make a note to follow up next week. You have the go-ahead on Gitcoin.

@speedyFixer
Copy link
Contributor

Great! :)

@gitcoinbot
Copy link

@speedyFixer Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

1 similar comment
@gitcoinbot
Copy link

@speedyFixer Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@speedyFixer
Copy link
Contributor

Hi @gitcoinbot I will start to work on Sunday.

@speedyFixer
Copy link
Contributor

Hi @gitcoinbot , I'm back from my travel, I will work on this today.

@rachelhamlin
Copy link
Contributor

Go go @speedyFixer :) thanks for checking in.

@gitcoinbot
Copy link

@speedyFixer Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@speedyFixer
Copy link
Contributor

Ok I'm going to stop in Gitcoin, Yes @rachelhamlin , I would like :)

@rachelhamlin
Copy link
Contributor

@speedyFixer cool! Any of these interest you?

#8998
#8940
#8930
#8877
#8718
#8662

@speedyFixer
Copy link
Contributor

#8877 sounds good :)

@rachelhamlin
Copy link
Contributor

@speedyFixer I added a bounty to #8877 - go for it!

@speedyFixer
Copy link
Contributor

Thanks @rachelhamlin , I stopped work on Gitcoin.

@gitcoinbot
Copy link

gitcoinbot commented Oct 14, 2019 •
edited
Loading

Issue Status: 1. Open 2. Cancelled

Work has been started.

These users each claimed they can complete the work by 2 months from now.
Please review their action plans below:

1) iamserver has been approved to start work.

will find the bug and fix it if you give me the permission to proceed

Learn more on the Gitcoin Issue Details page.

@rachelhamlin
Copy link
Contributor

Hey @iAmServer - apologies for my delay, I missed that you applied, but you're approved to start work if you're still interested.

@gitcoinbot
Copy link

@iAmServer Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@iAmServer
Copy link

Am in

@gitcoinbot
Copy link

@iAmServer Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

1 similar comment
@gitcoinbot
Copy link

@iAmServer Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@rachelhamlin
Copy link
Contributor

Hey @iAmServer! Checking in. Are you still on this one?

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

@iAmServer due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

1 similar comment
@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

@iAmServer due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@Serhy Serhy mentioned this issue Nov 13, 2019
Merged
8 tasks
@StatusSceptre
Copy link
Member

Hi @iAmServer are you still working on this issue?

@churik
Copy link
Member Author

churik commented Feb 25, 2020

Still relevant in nightly 25/02/2020

@churik
Copy link
Member Author

churik commented Apr 14, 2020

fixed in #10099

@churik churik closed this as completed Apr 14, 2020
@gitcoinbot
Copy link

Issue Status: 1. Open 2. Cancelled

The funding of 50.0 SAI (plus a crowdfund of 0.01 DAI worth 0.010038660500000001 USD) (50.0 USD @ $1.0/SAI) attached to this issue has been cancelled by the bounty submitter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@StatusSceptre StatusSceptre

Labels
group-chat
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@pedropombeiro @jakubgs @churik @annadanchenko @rachelhamlin @iAmServer @gitcoinbot @StatusSceptre @speedyFixer