Commit Graph

30 Commits (e995b7e3c49d706f57a439de657233b5d9bb6ac5)

Author SHA1 Message Date
David Barragán Merino e995b7e3c4 Use our get_object_or_404 function instead the django one 2015-01-29 10:31:41 +01:00
Alejandro Alonso bb40c528d7 Adding end points for getting projects by slug, tasks, userstories and issues by ref 2014-12-23 12:30:51 +01:00
Jesús Espino af1450ccf1 Refactor of tags queries using djorm-pgarray queries 2014-12-03 11:53:23 +01:00
Alejandro Alonso 6b33c30616 Fixing notifications __init__ because it was generating migration problems 2014-10-28 18:08:42 +01:00
Andrey Antukh ad7b231945 Fix HistoryResourceMixin class import. 2014-09-16 10:48:42 +02:00
Jesús Espino a9ecac7c1c Fixed bug #763: Now filter of us and issues filter by subject and reference 2014-08-28 11:24:19 +02:00
Jesús Espino 2817b3b120 Adding pre_save to the bulk actions 2014-08-11 20:19:38 +02:00
Alejandro Alonso 1d9d5b005f Allowing issue type ordering 2014-08-08 14:00:24 +02:00
Anler Hp 68a579338f Refactoring issues bulk creation 2014-08-01 15:02:10 +02:00
Anler Hp 0b02cc4523 Task #422 - Create issues in bulk 2014-07-29 13:43:57 +02:00
Anler Hp 4c2585a891 Task #396 - Filter issues by subject 2014-07-29 13:00:27 +02:00
Jesús Espino d97edb464c [HUGE CHANGE] Changed the permissions system 2014-07-24 12:19:06 +02:00
Anler Hp ac5e163dc5 Implement tags using pg arrays 2014-06-18 10:14:29 +02:00
Alejandro Alonso e534920c01 Optimistic Concurrency Control first approach 2014-06-17 16:08:59 +02:00
David Barragán Merino f9327c7069 Fix User model: delete first_name, last_name, permisions and groups, add full_name, and github_id, change description to bio 2014-06-12 12:16:36 +02:00
Andrey Antukh 3083b7f232 Notifications & History: modify all related models and resources for work with new api. 2014-06-12 00:12:15 +02:00
Jesús Espino c9706122a2 Removing things from the votes __init__ file 2014-06-05 17:51:52 +02:00
Anler Hp 9923e50603 Generic voting application
The stars application has been removed in favor of a more generic voting
application that works with any model. Starring a project is just a
special case of voting a project.

Usage.

Add a vote:

    votes.add_vote(<model instance>, user)

Remove a vote:

    votes.remove_vote(<model instance>, user)

Get the queryset of users that voted an object:

    votes.get_voters(<model instance>)

Get the number of votes an object has:

    votes.get_votes(<model instance>)

Get the objects of type <model> voted by an user:

    votes.get_voted(user, <model>)

The issues application is already making use of the votes application
through the following urls:

        /api/v1/issues/<id>/upvote      <- url name is "issues-upvote"
        /api/v1/issues/<id>/downvote    <- url name is "issues-downvote"
2014-06-02 12:03:09 +02:00
Anler Hp 8003abbbef Moving neighbors logic into standalone module 2014-05-22 18:34:03 +02:00
David Barragán Merino e8a2b9fbb3 Refactor attachments 2014-05-09 12:09:49 +02:00
David Barragán Merino 09eced41a0 Update notifications to use the new history module 2014-05-09 11:05:09 +02:00
Andrey Antukh 0529bf19c3 Replace license on taiga.projecrs.issues module. 2014-04-21 16:33:05 +02:00
Andrey Antukh 04fa6f6715 Downgrade to djangorestframework 2.3.13 and backport some usefull routers and decorators. 2014-03-22 18:38:30 +01:00
David Barragán Merino 449548696d US #70: Task #124: Show attachments info in the issues list 2014-03-08 19:48:00 +01:00
Jesús Espino d9ab184d0a Bug#199: Now work correctly the filtering of next/prev on retrieve actions 2014-03-07 14:15:57 +01:00
David Barragán Merino 225cfbc7a0 Minor improvements 2014-03-06 18:37:24 +01:00
ikame e9dfbe7378 US #50: Return neighbors when fetching an US/Issue
The response for an UserStory/Issue now contains:

{
    ...
    "neighbors": {
        "previous": {
            "id": ...,
            "ref": ...,
            "subject": ...
        },
        "next": {
            ... same as above
        }
    }
}

If there's a neighbor missing the response will contain the empty dict {}:

{
    ...
    "neighbors": {
        "previous": {},
        ...
    }
}

Neighbors are looked up applying the same filters defined in the
corresponding ViewSets and the same ordering defined in those filters or
ultimately, in the model's meta. In other words, using the same params
you use to filter the object list, can be used to filter the neighbors
when fetching the object's details.
2014-02-26 12:47:55 +01:00
Jesús Espino f2037bbc20 Adding type on issues filter 2014-02-16 16:51:27 +01:00
David Barragán Merino fffa8762c5 Bug #135: Now we can filter unassigned issues 2014-01-29 14:55:15 +01:00
Jesús Espino 99b9066965 US#49: Renaming app to Taiga 2014-01-27 17:33:43 +01:00