Lazylead alternatives and similar software solutions
Based on the "Project Management" category.
Alternatively, view Lazylead alternatives based on common mentions on social networks and blogs.
-
Gitea
Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD -
gitbucket
A Git platform powered by Scala with easy installation, high extensibility & GitHub API compatibility -
Gitolite
Hosting git repositories -- Gitolite allows you to setup git hosting on a central server, with very fine-grained access control and many (many!) more powerful features. -
Redmine
Mirror of redmine code source - Official Subversion repository is at https://svn.redmine.org/redmine - contact: @vividtone or maeda (at) farend (dot) jp -
UVDesk
UVdesk Opensource Community Helpdesk Project built for all to make a Full Ticketing Support System along with many more other features. -
Leantime
Leantime is a goals focused project management system for non-project managers. Building with ADHD, Autism, and dyslexia in mind. -
Bonobo Git Server
Bonobo Git Server for Windows is a web application you can install on your IIS and easily manage and connect to your git repositories. Go to homepage for release and more info. -
Tuleap
Tuleap is an Open Source Suite to improve management of software developments and collaboration. With a single web-based solution, project managers, developers & quality managers can easily build, deploy software projects. -
The Bug Genie
DISCONTINUED. The Bug Genie was a friendly project management and issue tracking tool, now replaced by Pachno -
Kallithea
Source code management system that supports two leading version control systems, Mercurial and Git, with a web interface. -
RhodeCode
RhodeCode is an open source platform for software development teams. It unifies and simplifies repository management for Git, Subversion, and Mercurial. -
sorcia
Sorcia is a minimalist web frontend for Git repositories with fine-grained user access controls, multiple themes to choose based on your taste and many more. -
Pagure
A lightweight, powerful, and flexible git-centric forge with features laying the foundation for federated and decentralized development. -
SCM Manager
The easiest way to share and manage your Git, Mercurial and Subversion repositories over http. -
ProjeQtOr
A complete, mature, multi-user project management system with extensive functionality for all phases of a project.
CodeRabbit: AI Code Reviews for Developers
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Lazylead or a related project?
Popular Comparisons
README
Overview
Ticketing systems (Github, Jira, etc.) are strongly integrated into our processes and everyone understands their necessity. As soon as a developer becomes a lead/technical manager, he or she faces a set of routine tasks that are related to ticketing work. On large projects this becomes a problem, more and more you spend time running around on dashboards and tickets, looking for incorrect deviations in tickets and performing routine tasks instead of solving technical problems.
The idea of automatic management is not new, but large companies/projects are not ready yet for such a decisive breakthrough and need step-by-step solutions such as lazylead. I think you remember how static code analysis treated at in the past; today we have a huge toolkit (pmd, checkstyle, qulice, rubocop, peon, etc) for each language that allows you to avoid routine issues and remove from the code reviewer the unnecessary load. The same logic we can apply to our day-to-day ticket management activities - let's reduce or even remove unnecessary routine actions.
Join our telegram chat lazylead for discussions.
Legend:
- ๐ด๐ฝ in-progress
- โ planned
- โ implemented
- ๐ต implemented, but not tested
- โ not supported/planned
Daily annoying task | Jira | Github | Trello | SVN | Git |
---|---|---|---|---|---|
[Notify ticket's assignee](lib/lazylead/task/alert/alert.rb) | โ | โ | โ | โ | โ |
[Notify ticket's reporter](lib/lazylead/task/alert/alert.rb) | โ | โ | โ | โ | โ |
[Notify ticket's manager](lib/lazylead/task/alert/alert.rb) | โ | โ | โ | โ | โ |
[Notify about illegal "Fix Version" modification](lib/lazylead/task/fix_version.rb) | โ | โ | โ | โ | โ |
[Expected comment in ticket is missing](lib/lazylead/task/missing_comment.rb) | โ | โ | โ | โ | โ |
[Propagate some fields from parent ticket into sub-tasks](.docs/propagate_down.md) | โ | โ | โ | โ | โ |
[Evaluate the ticket formatting accuracy](.docs/accuracy.md) | โ | โ | โ | โ | โ |
Print the current capacity of team into newly created tasks | โ | โ | โ | โ | โ |
Create/retrofit the defect automatically into latest release | โ | โ | โ | โ | โ |
[Notify about expired(ing) due dates](.docs/duedate_expired.md) | โ | โ | โ | โ | โ |
Notify about absent original estimations | โ | โ | โ | โ | โ |
Notify about 'Hot potato' tickets | โ | โ | โ | โ | โ |
Notify about long live tickets (aging) | โ | โ | โ | โ | โ |
Create a meeting(s) automatically in case some tickets appeared (group by assignee/reporters/component/ticket type/etc) | โ | โ | โ | โ | โ |
Propogate fields from parent tickets to sub-tasks | โ | โ | โ | โ | โ |
Notify about tickets without comments with expected text | โ | โ | โ | โ | โ |
[Notify about team loading (no tasks on teammates)](lib/lazylead/task/loading.rb) | โ | โ | โ | โ | โ |
Notify about tickets matches predefined multiple conditions | โ | โ | โ | โ | โ |
Link automatically the ticket and Confluence page if link found in ticket's comments/description | โ | โ | โ | โ | โ |
Notify about tickets assigned to your team members not by effective managers | โ | โ | โ | โ | โ |
Notify about modifications of important files in VCS | โ | โ | โ | โ | ๐ด |
Notify about diff changes for past X period in VCS | โ | โ | โ | โ | ๐ด |
Notify about changes with some text for past X period in VCS | โ | โ | โ | โ | ๐ด |
[Notify when someone outside of your team changed the due date on tickets for your team](lib/lazylead/task/micromanager.rb) | โ | โ | โ | โ | โ |
[Notify when someone outside of your team assigned a ticket directly to the developer](lib/lazylead/task/assignment.rb) | โ | โ | โ | โ | โ |
Integration | Type | Status |
---|---|---|
[Microsoft Exchange Server](lib/lazylead/exchange.rb) | Emails | โ |
[Microsoft Exchange Server](lib/lazylead/exchange.rb) | Calendar | โ |
[mail.yandex.com](lib/lazylead/postman.rb) | Emails | โ |
[mail.google.com](lib/lazylead/postman.rb) | Emails | ๐ต |
calendar.google.com | Calendar | โ |
slack.com | Notifications | โ |
GitHub | VCS + CI/CD | โ |
GitLab | VCS + CI/CD | โ |
BitBucket | VCS + CI/CD | โ |
New ideas, bugs, suggestions or questions are welcome via GitHub issues!
Get started
โ ๏ธ We're still in a very early alpha version, the API may change frequently until we release version 1.0
.
Let's assume that:
- your team is using jira as a ticketing system
- you defined a jira filter with tickets where actions need. The filter id is
555
and it has JQL liketext project=XXXX and type=Bug and status not in (Closed, Cancelled, "Ready For Testing", "On Hold) and parent = YYYY and duedate < startOfDay()
- you have
MS Exchange
server for email notifications - you want to notify your developers during working days at
8am (UTC)
time about tickets where due dates are expired
For simplicity, we are using docker-compose:
Define yml file with configuration [tasks.yml](.github/tasks.yml)
version: '2.3' services: lazylead: image: dgroup/lazylead:latest container_name: lazylead mem_limit: 128m environment: # The jira server details. # Please ensure that your jira filter(s) grants this user to see issues. # Sometimes jira filter(s) may be created with restricted visibility, thus # lazylead can't find the issues. jira_url: https://your.jira.com jira_user: theuser jira_password: thepass # The MS Exchange server details, please ensure that '/ews/Exchange.asm` # will be after your server url. Just change the url to your server. exchange_url: https://your.ms.exchange.server/ews/Exchange.asmx exchange_user: theuser exchange_password: the password volumes: - ./:/lazylead/db # db/ll.db is sqlite file with jira related annoying tasks entrypoint: bin/lazylead --sqlite db/ll.db --trace --verbose
or just download the project using git
git clone https://github.com/dgroup/lazylead.git ll && cd ll
Create a container, using
docker-compose -f .github/tasks.yml up
The container will stop as there were no tasks provided:ll > docker-compose -f .github/tasks.yml up Creating lazylead ... done Attaching to lazylead lazylead | [2020-08-09T06:17:32] DEBUG [main] Version: 0.5.0 lazylead | [2020-08-09T06:17:32] DEBUG [main] Memory footprint at start is 52MB lazylead | [2020-08-09T06:17:32] DEBUG [main] Database: '/lazylead/db/ll.db', sql migration dir: '/lazylead/upgrades/sqlite' lazylead | [2020-08-09T06:17:32] DEBUG [main] Migration applied to /lazylead/db/ll.db from /lazylead/upgrades/sqlite lazylead | [2020-08-09T06:17:32] DEBUG [main] Database connection established lazylead | [2020-08-09T06:17:32] DEBUG [main] SMTP connection established with {host} as {user}. lazylead | [2020-08-09T06:17:32] WARN [main] ll-001: No tasks found. lazylead | [2020-08-09T06:17:32] DEBUG [main] Memory footprint at the end is 67MB lazylead exited with code 0 ll >
Define your team and tasks in database. Yes, there are no UI yet, but its planned. Pull requests are welcome! The tables structure defined [here](upgrades/sqlite/001-install-main-lazylead-tables.sql). Modify you sqlite file(
ll.db
) using DB Browser or any similar tool. Please change the<youremail.com>
to your email address in order to be in CC when developer get the notification:insert into teams (id, name, properties) values (1, 'Dream team with lazylead', '{}'); insert into systems(id, properties) values (1,'{"type":"Lazylead::Jira", "username":"${jira_user}", "password":"${jira_password}", "site":"${jira_url}", "context_path":""}'); insert into tasks (name, schedule, enabled, id, system, team_id, action, properties) values ('Expired due dates', 'cron:0 8 * * 1-5', 'true', 1, 1, 1, 'Lazylead::Task::AssigneeAlert', '{"sql":"filter=555", "cc":"<youremail.com>", "subject":"[LL] Expired due dates", "template":"lib/messages/due_date_expired.erb", "postman":"Lazylead::Exchange"}');
Yes, for task scheduling we are using cron here, but you may use other scheduling types from rufus-scheduler.
Once you changed
./ll.db
, please restart the container usingdocker-compose -f .github/tasks.yml restart
ll > docker-compose -f .github/tasks.yml restart Restarting lazylead ... done
check the logs and stop container if needed
ll > docker logs lazylead lazylead | [2020-08-09T06:17:32] DEBUG [main] Version: 0.5.0 lazylead | [2020-08-09T06:17:32] DEBUG [main] Memory footprint at start is 52MB lazylead | [2020-08-09T06:17:32] DEBUG [main] Database: '/lazylead/db/ll.db', sql migration dir: '/lazylead/upgrades/sqlite' lazylead | [2020-08-09T06:17:32] DEBUG [main] Migration applied to /lazylead/db/ll.db from /lazylead/upgrades/sqlite lazylead | [2020-08-09T06:17:32] DEBUG [main] Database connection established lazylead | [2020-08-09T06:17:32] DEBUG [main] SMTP connection established with {host} as {user}. lazylead | [2020-08-09T06:17:32] DEBUG [main] Task scheduled: id='1', name='Expired due dates', cron='0 8 * * 1-5', system='1', action='Lazylead::Task::AssigneeAlert', team_id='1', description='', enabled='true', properties='{"sql":"filter=555", "cc":"[email protected]", "subject":"[LL] Expired due dates", "template":"lib/messages/due_date_expired.erb", "postman":"Lazylead::Exchange"}' ...
How to contribute?
Pull requests are welcome! Don't forget to add your name to contribution section and run this, beforehand:
rake -A
Everyone interacting in this projectโs codebases, issue trackers, chat rooms is expected to follow the [code of conduct](.github/CODE_OF_CONDUCT.md).
*Note that all licence references and agreements mentioned in the Lazylead README section above
are relevant to that project's source code only.