-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 0.7 swallows, 0.8 swallows, 0.20 Swallows
-
Fix Version/s: 0.8 swallows
-
Labels:None
Ban User
As administrator I might need to ban some users that are causing problems. This can be done on the Ban users page.
1. I click on Ban users and a page where I can prepare of users that should be banned.
2. I type an username, while typing auto-completion shows possible suggestion, matching what has been entered so far.
3. I select the user I want to ban from the suggestions and press add button.
4. The user is being listed in the table bellow, where the username, email, posts count and the date of registration. If I need to add more users I repeat step 2.
5. When I prepare the list of users that are to be banned, I decide:
a. to ban them for ever, by ticking the 'Permanent Ban' check box, then the ban length field gets disabled
b. to specify the length of the ban, by leaving the 'Permanent Ban' check box unticked.
6. I enter the reason for the ban.
7. I press submit, bans are applied to the user in the list below.
For more information check the user story description on http://confluence.jtalks.org/display/poulpe/0.7+Swallows+User+Stories
- relates to
-
POULPE-189 Banned user disappears from the list
-
- Closed
-
-
POULPE-254 Remove permanent ban checkbos and the input field for setting the amount of days
-
- Closed
-
-
-
- Closed
-
-
POULPE-416
[Users] Ban users
-
- Waiting for Review
-
1.
|
Write back-end code related to story "Ban user" |
|
Closed | Guram Savinov |
|
|||||||
2.
|
Write UI for banning a user |
|
Closed | Konstantin Akimov |
|
Was the reason of ban deleted from project functionality? There is nothing, where it should be. Is it OK?
Ban reason also was removed, I will try to find related issue
We just don't need them, it was a useless information. Also we changed the way we were banning. In the future we might return it, but as for now - we really don't care about ban reason.
v. 0.20: "Permanent ban" functionality wasn't implemented