No description provided.
Unidy SDK: API Client, Stencil Components, and React Wrappers
A high-performance ticket management system for Vibe Coding environment
A minimal Rust crate that gives any application agentic capabilities.
CLI project manager for running AI coding agents in parallel, isolated by design.
Core library for APM — a git-native project manager for parallel AI coding agents.
Web UI and agent dispatcher for APM, a git-native project manager for parallel AI coding agents.
Tickets in your Git repo, stored as git-meta metadata
Ticket-tracking metadata stored via git-meta
A CLI for fetching JIRA issue summaries, details, and current sprint tickets.
This is a command line application that can be used as a personal productivity tool for interacting with JIRA
A simple CLI tool to help you with your git workflow.
Used to configure htsget-rs by using a config file or reading environment variables.
ITSM MCP Server — tickets, incidents, change requests, SLAs, service catalog, knowledge articles, and routing for IT support agents
Make every ressource as a ticket with a status and a brief
Adding device_ticketable to your devise implementaton will integrate it with mod_auth_tkt for the Apache HTTP server by setting/destroying the necessary auth_tkt cookie
Wiki and Tickets
A ruby implementation of the Networked Help Desk API
Get access to Jira and Brouha ticketing systems through the single service
Wrapper for the Centaman Ticketing API
Event registrations, tickets and products
Proxy for tickets service
Communicate with customers through this gem
branch-name is a gem that provides a command-line interface that allows you to accomplish several tasks, tasks I personally find myself having to carry out every time I work on a feature branch. I created this gem for myself; however, you are free to use it yourself, if any of these tasks fits into your personal routine: 1. Formulate a git feature branch name, given a jira ticket and jira ticket description. Why? Because I am constantly having to create git feature branch names that are based on jira ticket and jira ticket descriptions. 2. Optionally create a "project" based on the branch name (formulated in step 1 above). Why? Because I'm constantly having to create folders to manage files associated with the feature branches I am working on. 3. Optionally use and manage default options that determine the git feature branch name formulated, project greated, and default files associated with the project.Why? Because I routinely have to create files to support the feature I am working on and associate them with the feature I am working on. For example: scratch.rb to hold scratch code, snippets.rb to hold code to execute to perform redundant tasks, and readme.txt files to document things I need to remember.
This gem provides a Ruby implementation of different integrations with ticketing services for Nexpose.
Provides Ruby wrappers for the Ticket Evolution API (http://developer.ticketevolution.com). Ticket Evolution is the industry leader in software for the Ticket Broker industry.