Skip to content

Alex Stanciu

My feedback

4 results found

  1. 20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Alex Stanciu commented  · 

    Also, allowing us to change the actual colors would be great. Blue and Yellow are somewhat useless since they are used for the top two rows and would be confusing to use below.

  2. 26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Alex Stanciu commented  · 

    I would also Vote for this, but have ran out of votes :(

    Here's our current workflow:
    My team is responsible for a product that is split across 5 github repos (5 components). We currently use ZenHub to get a view of all issues across the 5 repos.

    We could replace ZenHub if we can do the following workflow:

    - Import issues from 5 Repos into one board
    - PO Organizes/Prioritizes issues across Blue/Yellow stacks
    - PO Creates Releases
    - PO Pushes a Release to Pivotal tracker, where the engineering team works with a fine-grained detail
    - As issues are closed in Pivotal, they are reflected on the board in SOB

    Would be happy to build this myself on my end if you guys had an API :)

  3. 220 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Alex Stanciu commented  · 

    Hi Arpi

    There's 2 things that I would do with an API:

    1. Prioritization. If you have a LOT of cards (100's) it's very hard to order them with the current SOB UI. I have a custom tool that I built that grabs issues and maps them on a Value vs Effort chart, which produces a Score between -100 to 100, depending on the (x,y) possition on the chart. I then use this score to order the cards
    http://i.imgur.com/WTixUSY.jpg

    I currently have to export the board, run the xls file through my tool, re-import the board (loosing all colors in the process, btw). If I could make my tool read/write to an SOB API directly, would make life a lot easier

    2. GitHub integration. I know you guys are currently working on this, but we have boards with stories that span multiple github repos. If your integration won't allow hooking up to multiple repos, then I will need to use a GitHub webhook -> My own server -> SOB API to create or update stories on my board.

    Let me know if this helps

    An error occurred while saving the comment
    Alex Stanciu commented  · 

    Yes, this is REALLY needed. It would save me the hassle of Export - Excel -> CSV -> Write script to manipulate cards en mass -> Excel -> Import.... Ugh

    Alex Stanciu supported this idea  · 
  4. 26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Alex Stanciu commented  · 

    YES!!! Epics should be synced into the 2nd Row

Feedback and Knowledge Base