BigW Consortium Gitlab

  1. 16 Mar, 2017 1 commit
    • Add 'Undo mark all as done' to Todos · 5f9ace8e
      Jacopo authored
      Added the ability to 'Undo mark all as done' todos marked as complete with 'Mark all as done'
      in the 'Todo' tab of the Todo dashboard.
      The operation undos only the todo previously marked as done with the 'Mark al as done' button.
  2. 10 Mar, 2017 1 commit
    • Add 'Undo' to Todos in the Done tab · e20ffc6e
      Jacopo authored
      Added the ability to 'Undo' the todos marked complete in the 'Done' tab of the Todo dashboard.
      Added the ability to 'Undo mark all as done' todos marked complete with 'Mark all as done'
      in the 'Todo' tab of the Todo dashboard.
  3. 07 Mar, 2017 1 commit
  4. 21 Feb, 2017 1 commit
  5. 17 Feb, 2017 1 commit
    • Todo done clicking is kind of unusable. · 26160459
      Jacopo authored
      The Done button will change to an Undo button and the line item will be greyed out.
      Bold links will be unbolded.
      The user can undo the task by clicking the Undo button.
  6. 28 Jan, 2017 1 commit
  7. 27 Jan, 2017 1 commit
  8. 19 Jan, 2017 1 commit
    • Fix todos spec · 4f1eb8cd
      Sean McGivern authored
      This was changed in a community MR, but the branch was far enough behind
      master that it didn't have this spec.
  9. 22 Dec, 2016 1 commit
  10. 11 Nov, 2016 1 commit
  11. 04 Nov, 2016 1 commit
  12. 01 Nov, 2016 2 commits
  13. 28 Oct, 2016 1 commit
  14. 26 Oct, 2016 1 commit
  15. 03 Oct, 2016 1 commit
  16. 14 Sep, 2016 1 commit
    • Improve validity of spec/features/todos/todos_filtering_spec.rb · e7e628bf
      Robert Speicher authored
      Previously, we were checking that a CSS selector string didn't have some
      page-related content, which, of course it didn't.
      
      Now we check against the actual content of the selector, we use a more
      semantic selector, and we add an additional expectation for the text
      that _should_ be there, as an additional sanity check.
  17. 01 Sep, 2016 1 commit
  18. 31 Aug, 2016 1 commit
  19. 25 Aug, 2016 1 commit
  20. 19 Aug, 2016 1 commit
  21. 09 Aug, 2016 1 commit
  22. 17 Jun, 2016 1 commit
  23. 03 Jun, 2016 2 commits
  24. 02 Jun, 2016 4 commits
  25. 01 Jun, 2016 1 commit
    • Fix 404 page when viewing TODOs that contain milestones or labels in different projects · f8a3344d
      Stan Hu authored
      A user viewing the TODOs page will see a 404 if there are mentioned labels
      in multiple different projects. This is likely a caching bug and only occurs
      when Markdown rendering occurs across multiple projects, which is why it's so
      tricky to reproduce. This is what I think is happening:
      
      1. LabelReferenceFilter#references_in encounters label ~X for ProjectA and finds the label in the DB as id = 1.
      2. LabelReferenceFilter.references_in yields [1, 'X', nil, ...]
      3. Since project_ref is nil, AbstractReferenceFilter#project_from_ref_cache caches nil => ProjectA.
      4. LabelReferenceFilter#references_in encounters label ~Y for ProjectB and finds the label in the DB as id = 2.
      5. LabelReferenceFilter.references_in yields [2, 'Y', nil, ...]
      6. AbstractReferenceFilter#project_from_ref_cache lookups nil and returns ProjectA. It was supposed to be ProjectB.
      7. A is the wrong project, so the label lookup fails.
      
      This MR caches Markdown references if the key is present.
      
      Closes #17898
  26. 25 May, 2016 3 commits
  27. 27 Apr, 2016 1 commit
  28. 22 Apr, 2016 1 commit
  29. 18 Apr, 2016 1 commit
  30. 08 Apr, 2016 1 commit