Stories

Comment by jhbrown

Comment

Comment by jhbrown

One of the recurring problems my early users have had is the need to move data back and forth between DoomCheck and their organizational system, most commonly Jira. So you're right about that being a problem.

Integrations aren't an impossibility, but they do require some serious design work (see next paragraph.) My current focus is to get people who are not already-invested in some other system to use DoomCheck as a standalone system so I can make sure the fundamentals are solid and usable.

As food for thought, here's a sketch of a design for Jira integration:

To begin with, we have to address a conceptual difference between DoomCheck and Jira. DoomCheck is document-centric, and encourages many small estimates. You can easily write "Purchase laptop {0.5-1h}, install Ubuntu {1-10h}, check out monorepo and build codebase {1-4h}". In Jira, every issue or sub-task is heavyweight; it would be pretty ugly to try to create a sub-task for every estimate in the preceding sentence.

So my current notional design is to associate Markdown document sections with Jira issues and sub-tasks. The descriptive text within a given DoomCheck markdown section would go in the corresponding Jira issue/sub-task description -- fortunately Jira now supports Markdown formatting so no translation should be needed.

Results of DoomCheck's analyses would go in two places. First, when an analysis was run or rerun, the latest probability graphs would get added to each Jira issue in a comment. Second, key values (e.g. the 10%, 50%, and 75% hours-to-complete estimates) could get written directly into custom fields, optionally with one of them getting written directly into the Jira native estimation field.

This approach would allow for two-way information flow between DoomCheck and Jira. One notional workflow might be: 1. Estimate your project in DoomCheck. 2. Push button to create and populate a new project in Jira from your DoomCheck plan. 3. Push button occasionally to make DoomCheck pull updated information from Jira, re-estimate everything, and push resulting graphs and numbers back to Jira.

I'm glossing over a lot of details here, of course, but hopefully that gives you a rough idea of how it might work for one very popular PM tool.

Replies jhbrown · 2023-01-20
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.