sifterstudios/bitbucket-notifier

Issues

• Have a way to show how many PR's that doesn't have a comment or approval/needs work, that's NOT your own. Make it a sticky, make it show an top, make it stand out..

  #24 opened a year ago
  0

• feat: reduce number of api calls by checking whether the pr has a timebeforecompletion of > 0

  #23 opened a year ago
  0

• Refactor Actions string to constants cause it's better

  #22 opened a year ago
  0

• Get persistence for things already notified..!

  #21 opened a year ago
  0

• BUG: Not nofifying about first in comment thread, suspect that check for len(0)

  #20 opened a year ago
  0

• Create debug option for when running

  #19 opened a year ago
  0

• BUG: Wrong pr title in notification

  #18 opened a year ago
  0

• Handle errors in go better

  #17 opened a year ago
  0

• Add support for Dunst: https://dunst-project.org/

  #16 opened a year ago
  0

• Differentiate notification of pushed commit by commit and amend

  #15 opened a year ago
  0

• Implement storing of info on completiontime on PR's, we can probably not save info on PR's themselves due to security concerns, but time of completion should be OK I would think?

  #14 opened a year ago
  0

• Add possibility of notification when you're assigned a Defect from jira

  #13 opened a year ago
  0

• Try to find out if we can get which team the author of the pull request was on, then save some stats on time from creating to merge. And of course also for the author itself, to try to measure time saved

  #12 opened a year ago
  0

• Change frontend port to something not used by other apps

  #11 opened a year ago
  0

• Change call to inbox pr's to not have owner but keep `OPEN` status

  #10 opened a year ago
  0

• Add option in front-end for getting notified when someone pushes to a PR you've commented on (not your own)

  #9 opened a year ago
  0

• Get call to PR-activity

  #8 opened a year ago
  0

• Create Struct for saving data from both endpoints

  #7 opened a year ago
  0

• Make sure the folders for config and security files exist before adding files to them

  #6 opened a year ago
  0

• add settings that you can set from frontend to config

  #5 opened a year ago
  0

• Change button name in FE

  #4 opened a year ago
  0

• Change frontend to not do a call to bitbucket on refresh but rather get statistics from app backend. Alternatively, if no call has been made yet, do the call then.

  #3 opened a year ago
  0

• Make the get-calls in front-end async

  #2 opened a year ago
  0

• make a call to backend from frontend on refresh that updates state of settings to what's reflected in BE

  #1 opened a year ago
  0