Saravanan666/pypi-org huggingface dataset:
Package: jirachlog
# jirachlog## IntroductionCreates a basic changelog using git and Jira## PrerequisitesMake sure you have Python3.## InstallationRun command:pip3 install jirachlog## DevelopmentCreate and activate virtual environment:virtualenv venv
source venv/bin/activate
pip install -r requirements.txtTest the binary: (you can use your own Jira user)PYTHONPATH=. JIRA_SERVER=”https://jira.digitalroute.com/” JIRA_USERNAME=xxxx JIRA_PASSWORD=yyyy ./bin/jirachlog v1.5.0..v1.6.0 “Release 175 - Stream Linking” /Users/marcusj/code/dazzlerjs/dazzlerjs-apiYou can test the module by installing it locally:python setup.py bdist_wheel
/usr/local/bin/pip3 install ./dist/jirachlog-x.x.x-py3-none-any.whlReason for full path to pip3 is because we’re in a virtual envirionment when doing python development### Deploy new version to PyPiThis should be done by CI soon.python setup.py bdist_wheel
python -m twine upload dist/jirachlog-x.x.x-py3-none-any.whl
Package: jira-cli
IntroductionCommand line utility to interact with your jira instance.Documentation atread the docsDeprecation warningjira-cli, as of version2.1defaults to using the new command line interface.
The command line interface presented by versions up to0.4.2will be maintained (but only accessible if the--v1flag is passed in or the following snippet exists in the config file):[jira]
v1 = True
Package: jiraclui
jiracluijiracluiis a Command Line Interface (CLI) tool designed to interact with Jira, allowing users to efficiently manage tickets across various projects. This tool provides features such as fetching tickets, displaying them in a CLI table with customizable filtering options, updating ticket statuses, creating new tickets, and viewing ticket details – all directly from the command line.FeaturesTicket Retrieval:Retrieve tickets from different Jira projects and display them in a convenient CLI table.Filtering:Easily filter tickets based on column values in the CLI table, providing a flexible way to focus on specific information.Status Update:Update the status of Jira tickets directly from the command line.Ticket Creation:Create new Jira tickets using the CLI, streamlining the process of adding tasks to your projects.Ticket Details:View detailed information about a specific ticket, helping users get a comprehensive overview of individual issues.ConfigurationThejiracluitool supports a configuration file (config.yaml) that allows users to customize various aspects of the application. Here are some of the configurable options:Project Names:Specify the Jira projects from which tickets should be fetched.Users List:Optionally provide a list of users to filter tickets specifically for those users.Jira API URL:Set the URL of your Jira instance to connect and fetch data.Jira API Token:Securely authenticate with Jira using an API token.Application Options:Max Table Entry:Limit the number of entries displayed in the CLI table.App Colors:Customize colors for different parts of the application, such as the table, menu, details form, and prompts.InstallationTo usejiraclui, follow these steps:Install the package:Install thejiracluipackage using your preferred package manager. Open a terminal and run:pip install jiracluiGenerate a configuration file:Create aconfig.yamlfile to customize your Jira settings and preferences. You can generate a sample configuration using the--generate-configoption:jiraclui --generate-config -c config.yamlOpen the generatedconfig.yamlfile and customize it with your Jira instance details, including project names, users list, Jira API URL, and API token.Run thejiracluitool:Execute the following command in the terminal:jiraclui -c config.yamlThe application will use the specified configuration to connect to your Jira instance and provide a powerful command-line interface for interacting with your tickets.Set up an alias for easy access:For enhanced usability, you can add an alias to your shell configuration file (e.g.,.bashrcor.zshrc). Open the configuration file using a text editor and add the following line:alias jiraclui='jiraclui -c /path/to/your/config.yaml'Replace/path/to/your/config.yamlwith the actual path to yourconfig.yamlfile. After saving the configuration file, you can use thejiracluialias directly in the terminal:jiracluiThis alias simplifies the command and allows for quick access to your Jira CLI with the specified configuration.
Package: jiracmd
jiracmdJira Command Line ToolInstallationInstall this tool usingpip:$ pip install jiracmdUsageUsage instructions go here.DevelopmentTo contribute to this tool, first checkout the code. Then create a new virtual environment:cd jiracmd
python -m venv venv
source venv/bin/activateOr if you are usingpipenv:pipenv shellNow install the dependencies and test dependencies:pip install -e '.[test]'To run the tests:pytest
Package: jira-context
Do you have command line applications which interact with JIRA servers?
Do your users have to enter their credentials every time they run your
applications? Are you unable to use OAuth because your command line
application is open sourced or you have no way of securing the consumer
secret?Hi, Robpol86 here for jira-context. The easy way to prompt for
credentials and cache session cookies on your clients’ workstations.jira-contextis supported on Python 2.6, 2.7, 3.3, and 3.4.QuickstartInstall:pipinstalljira-contextUsage# example.pyfrom__future__importprint_functionimportsysfromjira_contextimportJIRAserver='https://jira.company.local'query='assignee = currentUser() AND resolution = Unresolved'iflen(sys.argv)==2:JIRA.FORCE_USER=sys.argv[1]print('Connecting to: '+server)withJIRA(server=server)asj:ifj.ABORTED_BY_USER:print('Aborted by user.',file=sys.stderr)sys.exit(1)issues=j.search_issues(query,maxResults=5)forissueinissues:print(issue.key,issue.fields.summary)$ python example.py
Connecting to: https://jira.company.local
JIRA username: does_not_exist
JIRA password:
Authentication failed or bad password, try again.
JIRA username:
Aborted by user.
$ python example.py $USER
Connecting to: https://jira.company.local
JIRA password:
FAKE-659 service solahart hp 082113812149
FAKE-620 Need new version to be compatible in Jira 6.3.1
FAKE-525 Half page become blank when Activity Stream gadget view as Wallboard
FAKE-468 create page and with custom fields
FAKE-022 As a burndown gadget I should support GH 6.0+
$ python example.py
Connecting to: https://jira.company.local
FAKE-659 service solahart hp 082113812149
FAKE-620 Need new version to be compatible in Jira 6.3.1
FAKE-525 Half page become blank when Activity Stream gadget view as Wallboard
FAKE-468 create page and with custom fields
FAKE-022 As a burndown gadget I should support GH 6.0+Class AttributesPersistedThese attributes/variables are persisted throughout the lifetime of
the currently running process. If you’ve got twowithblocks andABORTED_BY_USERbecomes True in the first one,
the second block will skip authentication.NameDescription/NotesABORTED_BY_USERFalse by default. Becomes True ifUSER_CAN_ABORTis True and the user enters a blank username or password.COOKIE_CACHE_FILE_PATHFile path to the cache file used to store the base64 encoded session cookie.FORCE_USERIf set to a string, user won’t be prompted for their username.USER_CAN_ABORTSet to False if you don’t want the user to continue without a JIRA session if they enter a blank user/pass.InstanceThese attributes are persisted only in the current JIRA() instance.NameDescription/Notesprompt_for_credentialsInstantiate with False if you don’t want the user prompted for credentials (useful in threads).authentication_failedBecomes True ifprompt_for_credentialsis False and cached cookies were invalid/missing.
Package: jiractl
The command line interface for Jira REST APIUsageRequirementsjira>=1.0.10pbr>=1.6cliff>=1.18.0InstallAutomatedjiractlcan be installed througheasy_installorpip.pipinstalljiractlManualClone thexmlsecrepository to your local computer.gitclonegit://github.com/bgaifullin/python-jiractl.gitChange into thejiractlroot directory.cd/path/to/jiractrlInstall the project and all its dependencies usingpip.pipinstall.LicenseUnless otherwise noted, all files contained within this project are liensed under the MIT opensource license.
See the included file LICENSE or visitopensource.orgfor more information.
Package: jiradata
Jira dataCause sometimes you need to sort out your issuesInstallpip install jiradataHow to use ?Write a csv reportcatresponse.json|jiradatamyreport.csvWith some 'Epic' and issue related to it :catresponse.json|jiradata--epic-fieldcustomfield_10000report.csvHold up what is thisreponse.json?They are issues in json format retrieved using the JIRA REST API.What I found convenient is to use thesearch APIwith JQL.For example, usinghttpie:config.json{"jql":"project = QA","startAt":0,"maxResults":2,"fields":["id","key"]}Command linecatconfig.json|http-amyusernamepost'https://<site-url>/rest/api/2/search'RelatedExport results to microsoft ExcelJira python
Package: jira-easy-api
jira_easy_apiA wrapper around Jira API to run jira commands missing in their UI as onelinersInstallationUse the package managerpipto install jira_easy_api.pipinstalljira_easy_apiUsagefromjira_easy_api_coreimportJiraClientjira_api_token="2pU1YDiGagbISzfGgDzfzE5C"jira_workspace_url='https://your_workspace.atlassian.net'jc=JiraClient(jira_workspace_url,"your_email@gmail.com",jira_api_token)#Initialize Jira Clientissues=jc.get_all_issues_by_project_name("FP")#Get all issues/tasksjc.create_new_issue("FP","Test task","It works!")#Create new issue/taskjc.update_issue_by_name("FP-377",{"description":"Test"})#Update existing issue/taskissues=jc.get_all_issues_by_project_name("FP")issue_ids=[str(issue)forissueinissues]ContributingPull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.LicenseMITCurrently implementedGet all issuesCreate new issueUpdate issueDelete issue
Package: jira-exporter
This package exports metrics aboutJiraissues asPrometheusmetrics.UsageConfigure API tokenYou’ll need to provide an API token to access the Jira REST API.
Currently HTTP Basic authentication is used.
See theJira documentationfor details.Start HTTP serviceStart the HTTP server like this:$ JIRA_URL=https://example.atlassian.net JIRA_USERNAME=test@example.com JIRA_PASSWORD=APITOKEN jira_exporter --host=127.0.0.1 --port=9653Pass--ttl=SECONDSto cache API results for the given time or -1 to disable (default is 600).
Prometheus considers metrics stale after 300s, so that’s the highest scrape_interval one should use.
However it’s usually unnecessary to hit the API that often, since the vulnerability alert information does not change that rapidly.You can restrict which projects to look at by passing a comma-separated list of project keys (FOO,BARetc.) with--projects.Configure Prometheusscrape_configs:
  - job_name: 'jira'
    scrape_interval: 300s
    static_configs:
      - targets: ['localhost:9653']We export one metric, a gauge calledjira_issues_total,
with labels{project="PROJ",status="open"}.Additionally, ajira_scrape_duration_secondsgauge is exported.CHANGES1.1.0 (2020-07-31)Make projects configurable.1.0.1 (2019-10-30)Use correct listen port.1.0.0 (2019-10-30)First release.
Package: jira-freeplane
Page ContentsSoftware RequirementsInstallationPythonDocker - jira-freeplaneQuickstartdocker (interactive mode)python/pipContributeSupportLicenseSoftware RequirementsFreeplanePick onePythonDockerInstallationPythonpipinstalljira_freeplaneDocker -jira-freeplanedockerpullhollingsworthsteven/jira-freeplaneQuickstartCreate a new mindmap, seesample.mmas an example.If you want to start non interactive (with an ini file) you can find oneheredocker (interactive mode)TipThis assumes you are running bash or zsh as your shellReplace$mindmapwith the file name / path of your mindmap.Replace$JIRA_USER, and$JIRA_PASSwith your JIRA credentials.(You can also use environment variables if you do not want them to show in
your command history)do not change/config/freeplane_doc.mmonly$mindmapdockerrun--rm-it-v"$(pwd):/app"-v"$mindmap:/config/freeplane_doc.mm"-e"JIRA_USER=${JIRA_USER}"-e"JIRA_PASS=${JIRA_PASS}"-u"$(id-u):$(id-g)"hollingsworthsteven/jira-freeplanejira-freeplane--interactive/config/freeplane_doc.mmpython/pipTipreplace<your_jira_username>and<your_jira_password>with your JIRA credentials.pipinstalljira_freeplaneexportJIRA_USER=<your_jira_username>exportJIRA_PASS=<your_jira_password>jira-freeplane-i/path/to/mindmap.mmContributePull requests are welcome!Issue TrackerSource CodeSupportUnfortunately, there is no support for this project. We do welcome
contributions and pull requests though!LicenseThe project is licensed under the MIT license.
seeLICENSE
Package: jirafs-latex
This plugin provides two latex features for Jirafs –Automatically conversion of latex documents into PDF documents before
uploading the PDF to JIRA.A{latex}macro block you can use in comments and ticket descriptions for
embedding inline images or PDFs into your text.InstallationInstall from PIP:pip install jirafs-latexEnable for a ticket folder:jirafs plugins --enable=latexNote that you can globally enable this (or any) plugin by adding the--globalflag to the above command:jirafs plugins --global --enable=latexRequirementsRequiresxelatex.Using the Automatic Latex CompilerSimply place a file with a.texextension in your ticket folder.  It’ll
be compiled into a PDF automatically, and the PDF will be uploaded to JIRA
(not the.texfile) next time you push changes to JIRA.Using the{latex}Macro BlockEnter a latex block like so:{latex:name=somefilename.pdf}
\documentclass{article}
\usepackage{graphicx}

\begin{document}

\title{Introduction to \LaTeX{}}
\author{Author's Name}

\maketitle

\begin{abstract}
The abstract text goes here.
\end{abstract}

\section{Introduction}
Here is the text of your introduction.

\begin{equation}
    \label{simple_equation}
    \alpha = \sqrt{ \beta }
\end{equation}

\subsection{Subsection Heading Here}
Write your subsection text here.

\begin{figure}
    \centering
    \includegraphics[width=3.0in]{myfigure}
    \caption{Simulation Results}
    \label{simulationfigure}
\end{figure}

\section{Conclusion}
Write your conclusion here.

\end{document}
{latex}The above will be replaced with inline image JIRA markup (in this case,!somefilename.pdf!) when submitting these changes to JIRA.Youmustspecify anameparameter in your opening{latex}tag;
that’s the filename that will be uploaded to JIRA next time you submit changes.
Also, note that if you have thestandalonelatex plugin installed
and use it to convert your latex documents into PNG images instead, you
should specify a filename ending inpngin yournameparameter.This is probably not important to you, but if you’re curious about how this
works: what is happening here is the plugin writes your latex content
to a file, then asks xelatex to compile your document, then once that process
has completed, all filesexceptthe one matching the name you’ve submitted
are deleted.  After this point, everything works exactly as it does when
you’re uploading a normal file.
Package: jirafs-pandoc
Jirafs-Pandoc=============Automatically converts many kinds of markup into fancy PDF fileswhen uploading to JIRA.For example: it transforms`markup like this <https://s3-us-west-2.amazonaws.com/coddingtonbear-public/github/jirafs-pandoc/pdf_example.rst>`_into `markup like this <https://s3-us-west-2.amazonaws.com/coddingtonbear-public/github/jirafs-pandoc/pdf_example.pdf>`_.Installation------------1. Install from PIP::pip install jirafs-pandoc2. Enable for a ticket folder::jirafs plugins --enable=pandocNote that you can globally enable this (or any) plugin by adding the``--global`` flag to the above command::jirafs plugins --global --enable=pandocRequirements------------Depending upon which output format you utilize, your requirementsmay vary:* **PDF Output**: Both pandoc and xelatex are required.* **Other output formats**: Only pandoc is required.Supported Input Formats and Extensions--------------------------------------* Text Formats (``extra``)* ``*.text``* ``*.txt``* HTML (``html``)* ``*.html``* ``*.htm``* JSON (pandoc AST) (``json``)* ``*.json``* Latex (``latex``)* ``*.latex``* ``*.tex``* ``*.ltx``* Markdown (``markdown``)* ``*.markdown``* ``*.mkd``* ``*.md``* ``*.pandoc``* ``*.pdk``* ``*.pd``* ``*.pdc``* Native Pandoc (``native``)* ``*.hs``* reStructuredText (``rst``)* ``*.rst``* Textile (``textile``)* ``*.textile``Supported Output Formats------------------------Common output formats include:* PDF (``pdf``)* HTML (``html``)* RTF (``rtf``)But, you can use any output format supported by Pandoc.  Please checkwhich formats your version of Pandoc supports by running::pandoc --helpOptional Configuration----------------------* Default Input Formats: markdown, reStructuredText, and textile.See `Configuring Input Formats`_ for details on how to limit orexpand which files will be transformed.* Default Output Format: PDF.  See `Configuring Output Format`_ fordetails on how to set which output format will be used.Configuring Input Formats~~~~~~~~~~~~~~~~~~~~~~~~~By default, only markdown, reStructuredText, and textile filesare transformed, but you can change which files will be transformed on aformat or extension basis using either the``pandoc.enabled_input_extensions`` or the ``pandoc.enabled_input_formats``settings.To limit to only specific extensions, set the``pandoc.enabled_input_extensions`` setting; for example, to only transformreStructuredText and textile documents into PDFs, you would run::jirafs config --set pandoc.enabled_input_extensions rst,textileTo limit to only specific formats, set the``pandoc.enabled_input_formats`` setting.  To limit to transforming onlymarkdown and textile documents, you could run::jirafs config --set pandoc.enabled_input_formats markdown,textileConfiguring Output Format~~~~~~~~~~~~~~~~~~~~~~~~~By default, markup files will be converted into PDF files, but you canconvert to HTML (or any other supported format) instead by setting the``pandoc.output_format`` setting::jirafs config --set pandoc.output_format html
Package: jirafts
jiraftsJIRA Full Text Search is a tool which allows you to save issues to your local drive
for searching in indexed text with greatWhooshsearch engine or grep by regular expressions.Current stateWork in progress, but can be used alreadyInsstallation# in virtual env$pipinstalljiraftsUsageWe will use Cassandra's Python driver Jira as examplehttps://datastax-oss.atlassian.net/First, sync issues from projectPYTHON$ jirafts sync --url https://datastax-oss.atlassian.net/ -p PYTHONData will be stored to default location~/.jirafts/default_index/Now you can search issues$jiraftssearchsegmentation
$jiraftssearch"doesn't work"$jiraftssearch"status:'In Progress' asyncio"Grep with regexps$jiraftsgrep"CREATE KEYSPACE.*?SimpleStrategy"$jiraftsgrep-i"simplestra"Or dump whole text if you would like to process it$jiraftsdump|wc-l
$jiraftsdump-s|sortUsage with private JIRAAuthentication is supported via--authparameter$ jirafts sync --url https://private-project.atlassian.net/ --auth email@example.com:token-or-passwordAlso, you can pass path to file to--authwith credentials in same format$ jirafts sync --url https://private-project.atlassian.net/ --auth ~/.jira-auth.txtDescription of other options available in the integrated help:$jirafts--help
$jiraftssync--help
$jiraftssearch--help
$jiraftsgrep--help
$jiraftsdump--help
Package: jira-git-branch-namer
Jira Git branch Namerjira-git-branch-nameris a Python package designed to simplify the process of generating Git branch names based on Jira issue information.FeaturesConverts Jira issue titles into Git branch names.Supports various Jira issue types such as features, issues, and hotfixes.Truncates and sanitizes branch names for compatibility with Git.Interactive command-line interface for easy use.Installationpipinstalljira-git-branch-namerUsagejira-git-branch-namerExample:SelectissueType:1.feature2.issue3.hotfix
Enterjiraissuetitle:ExampleIssueTitle
Enterjiraissuenumber:ABC-123
GitBranchName:feature/ABC-123-example-issue-titlePublish In PyPiThis package has been Publish inPyPiContributingContributions are welcome! Feel free to submit bug reports, feature requests, or contribute code onGitHub.LicenseThis project is licensed under the MIT License - see theLICENSEfile for details.Feel free to add more sections or customize it further based on the specifics of your package. The README serves as a valuable resource for users to understand your project, so make it informative and user-friendly.
Package: jira-history
Makes working with Jira issue changelogs a breeze!Quickstart>>> issue = jira.issue('JIRA-2204')
>>> add_history(issue)
>>> issue.history
<Changelog 3 entries>
>>> issue.history.at(day)
{'resolution': ...}InstallationSimply runpip install jira-historyContributingPlease do! I would love for this to be developed further by anyone who is interested. Wherever possible, please
provide unit tests for your work (yes, this is very much a ‘do as I say, not as I do’ kind of moment).
Don’t forget to add your name to AUTHORS.LicenseCopyright (c) 2016 Sebastian RahlfPermission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the “Software”), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Package: jira-history-api
The Jira History library allows you to retrieve issues from JIRA in (almost) the same
state as they were on the requested date/time.In addition, a simple CLI is added to retrieve the status of a singular issue.Installation$pipinstalljira-history-apiExamplefromjira_historyimportJirafromdatetimeimportdatetimejira=Jira(url='https://jira-instance.com',username='bob',password='secret')jira.get_issue(key='ISSUE-100',datetime.strptime('12/11/2018 09:15:32','%d/%m/%Y %H:%M:%S'))UsageUsage: jira-history [OPTIONS]

Options:
-u, --username TEXT    Username that is able to query Jira  [required]
-p, --password TEXT    Password associated with the Username that is able to
                        query Jira  [required]

-s, --server TEXT      Jira server URL  [required]
-k, --key TEXT         Issue key to analyse  [required]
-d, --date [%Y-%m-%d]  Status of Jira issue key should reflect this date.
--verbose              Increase verbosity for more logging
--help                 Show this message and exit.CreditsTheatlassian-python-apiproject, providing the Jira REST API calls used by this project.
Package: jirahub
Jirahub: a package for syncing JIRA tickets and GitHub issuesThis package provides a configurable tool for syncing tickets in a JIRA project and issues in a GitHub repository.Please seethe documentationfor more informationLicenseThis project is Copyright (c) Association of Universities for Research in Astronomy (AURA) and licensed under the terms of the BSD 3-Clause license. SeeLICENSE.rstfor more information.