BigW Consortium Gitlab

  1. 15 Aug, 2016 1 commit
  2. 02 Aug, 2016 1 commit
  3. 01 Aug, 2016 2 commits
    • Redirect to external issue tracker from `/issues` · a70431f8
      Robert Speicher authored
      Prior, in order to display the correct link to "Issues" in the project
      navigation, we were performing a check against the project to see if it
      used an external issue tracker, and if so, we used that URL. This was
      inefficient.
      
      Now, we simply _always_ link to `namespace_project_issues_path`, and
      then in the controller we redirect to the external tracker if it's
      present.
      
      This also removes the need for the url_for_issue helper. Bonus! :tada:
    • State specific default sort order for issuables · 84a3225b
      zs authored
      Provide more sensible default sort order for issues and merge requests
      based on the following table:
      
      | type           | state  | default sort order |
      |----------------|--------|--------------------|
      | issues         | open   | last created       |
      | issues         | closed | last updated       |
      | issues         | all    | last created       |
      | merge requests | open   | last created       |
      | merge requests | merged | last updated       |
      | merge requests | closed | last updated       |
      | merge requests | all    | last created       |
  4. 27 Jul, 2016 1 commit
  5. 26 Jul, 2016 5 commits
  6. 14 Jul, 2016 2 commits
  7. 12 Jul, 2016 1 commit
  8. 01 Jul, 2016 1 commit
  9. 24 Jun, 2016 3 commits
    • Support for rendering/redacting multiple documents · d470f3d1
      Yorick Peterse authored
      This commit changes the way certain documents are rendered (currently
      only Notes) and how documents are redacted. Previously both rendering
      and redacting would run on a per document basis. The result of this was
      that for every document we'd have to run countless queries just to
      figure out if we could display a set of links or not.
      
      This commit changes things around so that redacting Markdown documents
      is no longer tied into the html-pipeline Gem. This in turn allows it to
      redact multiple documents in a single pass, thus reducing the number of
      queries needed.
      
      In turn rendering issue/merge request notes has been adjusted to take
      advantage of this new setup. Instead of rendering Markdown somewhere
      deep down in a view the Markdown is rendered and redacted in the
      controller (taking the current user and all that into account). This has
      been done in such a way that the "markdown()" helper method can still be
      used on its own.
      
      This particular commit also paves the way for caching rendered HTML on
      object level. Right now there's an accessor method Note#note_html which
      is used for setting/getting the rendered HTML. Once we cache HTML on row
      level we can simply change this field to be a column and call a "save"
      whenever needed and we're pretty much done.
  10. 14 Jun, 2016 2 commits
  11. 03 Jun, 2016 4 commits
  12. 06 May, 2016 1 commit
  13. 30 Apr, 2016 1 commit
  14. 28 Apr, 2016 1 commit
    • Load the "New Branch" button asynchronously · 04266470
      Yorick Peterse authored
      This button depends on Issue#can_be_worked_on? which in turn depends on
      Issue#related_branches. By rendering this button asynchronously we can
      finally remove all usages of Issue#related_branches and
      Issue#referenced_merge_requests from the issues "show" page.
  15. 22 Apr, 2016 1 commit
  16. 21 Apr, 2016 1 commit
  17. 20 Apr, 2016 2 commits
    • Add due_date:time field to Issue model · 3afd0817
      Mehmet Beydogan authored
      Add due_date text field to sidebar issue#show
      Add ability sorting issues by due date ASC and DESC
      Add ability to filtering issues by No Due Date, Any Due Date, Due to tomorrow, Due in this week options
      Add handling issue due_date field for MergeRequest
      Update CHANGELOG
      Fix ambigous match for issues#show sidebar
      Fix SCREAMING_SNAKE_CASE offenses for due date contants
      Add specs for due date sorting and filtering on issues
    • Label text color comes from JSON · 75626d5f
      Phil Hughes authored
      Created issuable singleton to house the filtering
  18. 19 Apr, 2016 1 commit
  19. 18 Apr, 2016 1 commit
  20. 13 Apr, 2016 2 commits
  21. 12 Apr, 2016 1 commit
    • Refactor `Issue#related_branches` · 5d88de09
      Timothy Andrew authored
      - Previously, the controller held the logic to calculate
        related branches, which was:
      
        `<branches ending with `issue.iid`> - <branches with a merge request referenced in the current issue>`
      
      - This logic belongs in the `related_branches` method, not in the
        controller. This commit makes this change.
      
      - This means that `Issue#related_branches` now needs to take a `User`.
        When we find the branches that have a merge request referenced in the
        current issue, this is limited to merge requests that the current user
        has access to.
      
      - This is not directly related to #14566, but is a related refactoring.
  22. 25 Mar, 2016 5 commits