> In a Jira workflow, there's a lot of customization required and a lot of thought needed to go into how to set up your workflow. Leantime is intended to be "op

> In a Jira workflow, there's a lot of customization required and a lot of thought needed to go into how to set up your workflow. Leantime is intended to be "opinionated" in the way that it's already set up I'm not sure what this means entirely, but across our projects we have some with different workflows than the others. These are necessary in that we have certain workflows that must meet compliance requirements, and those workflows are the best way to ensure we execute those. In other projects, they are less onerous and apply to different kinds of work (so, different workflows.) > Our "home" screen is intended for individual users to have pre-defined organization and not needing to set up their own dashboards This is good, but we generally keep our exec leadership out of JIRA (they don't really have the context for the details.) Our users can design their own dashboards, but that's a personal preference. We use the standard views. > making the goals and work more clear I would prefer to see more fall-into-the-pit-of-success for the equivalent of JIRA stories to be more oriented toward the outcome or feature or capability, as opposed to the accounting/I-got-receipts feeling I get from JIRA. While story points are fine, I prefer a focus on clarity and a better measurement for effort than the subjectivity of a team's interpretation of the fibonacci sequence. > for Confluence fans, we come default with docs and (on cloud) we have whiteboards So, Leantime includes a markup engine as well as a whiteboard feature? If I already have a deep investment in other tools that do those things, how do they integrate?