Before raising any bug be sure that you used the latest release and that it still reproduces with the latest master. No other version is supported.

Describe the bug
The docs refer to Dash support, but link is broken see #687

To Reproduce
Repro steps in #687 still work.

We use PivotalTracker at my workplace to manage stories/issues to work on. I'd love to be able to use Super Productivity to coordinate this work, but, an integration does not yet exist.

Pivotal has an API: https://www.pivotaltracker.com/help/api#top

I've noticed that there are some fields on some of the types, in particular the Comment struct, that are strings instead of a jira.Time. Is there a reason for this? It would be a breaking change, but would you be open to a pull request to change these fields to be jira.Time instead?

Small enhancement request: when I pull a list of issues, the Status is formatted as standard text right next to the title, which is less readable:

Perhaps it should get its own column? Or maybe bolded, and followed with a ":"

When a pod is killed, Jira doesn't clean up its lock file in the home directory. Atlassian's own documentation (well, blog post) shows a bootstrap script that removes the existing lock file, if found. Should we do the same here?

In https://github.com/atlassian-api/atlassian-python-api/blob/master/docs/confluence.rst I could not find the documentation for the expand= parameter.

I want to get the page content and I had to read the source code to find that confluence.get_page_by_id(page_id, expand='body.storage') does what I want.

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem.
  • Checked that your issue isn't already filed.
  • Filled the form.
  • Included logs and system information.

Description

When starting a setup with the provided docker-compose.yml everything starts as expected. However, Jira complains,

Description

Atlassian is working on v3 of the Jira Api.
By default, most of the functions will use it in favor of v2, as the URL uses latest.

https://developer.atlassian.com/cloud/jira/platform/rest/v3

v3 is currently marked as experimental

ToDo

• figure out what changed
• document what is new (as feature requests)
• ensure nothing (including tests) do

I've been trying to evaluate whether to use this package or jira-connector, and the main differentiator for my team's purposes seems to be that this includes a bunch of files in the docs directory for no clear reason. This includes a six megabyte source-mapping file in docs/ast/source.

I can't think of any reason why the docs, already hosted on [jira-node.github.io](https://jira-node.gi

Hi I'm not sure if I'm missing a trick here but it's not clear how to complete the log in step. Can you please clarify?

Does jira-dependency-graph support Jira Cloud, Jira Server, or both?

I notice the API documentation linked is that for Jira Server. I would like to use jira-dependency-graph with Jira Cloud, but I got a 401 error when I tried. It would be helpful if the README made it clear which product(s) are supported.

Thanks!

Hi All,

Is it possible to have feature such that it will update the priority field of the jira ticket when the severity of alert is changed.

Example use case is when I have two alerts defined with same name and different severity levels similar to this

Allow editing of story point for a story in JIRA, currently it's display only

The documentation lists two ways to create an issue:

jira issue create and jira create.

When I run the first form, jira issue create, I get an error:

Error: Issue does not exist or you do not have permission to see it.

I assume the docs are out of date?