Nic Brough -Adaptavist- Expert

What do you mean by "track status" and "track the change history"? What are you actually looking for here? And why? What benefit is it to the end user?

Set up Github to issue "transition issue" calls to Jira over REST.

Yes. To log time on an issue, a person just needs to be pulled into the "can log time" permission in the projects permission scheme. (via group, project role, dynamic role or any of the other options in the scheme)

So your issue here is network latency. There's nothing you can do about that other than get a faster network.

What do you mean by "web hook"? And why are you looking at this instead of securing your Jira? If you are on Cloud, then what did you do to allow the attack?

Try running your browser in "safe mode" with all your add-ons disabled. Then try another browser if that does not fix it.

You don't. Clone does what the word suggests - it creates a copy of the issue being cloned. There's no conditions or editing or changes, it simply creates a copy.

It is possible, but it really does not work well. Confluence does not yet tolerate the latency or unreliability of geographically remote nodes. You will end up with corrupted data if you do this.

If you want help with this, you'll have to explain what is wrong. Please read the last paragraph of my original answer.

"Network is unreachable" simply means that your client machine cannot get to the target over your network. This is almost always caused by a local network problem - your machine is simply not on the internet. Try ssh -vvv <target> This gives you a suprising (and yet boring) information about the connection!

Apologies for the age of this. You'll need to explain "ISR", what "integration" you are using to push them to Jira, how it is configured and so-on.

You are not going to be able to validate Edit actions over REST, best you can do, as I said, is to prevent issues that have had invalid data set from progressing further through the workflow until corrected. You can validate fields on create issue, add validators to the create transition. There are no conditional edits in…

Next-gen doesn't support that yet.

No. I don't think Atlassian are going to do this, because if you sort by something other by ranking, it's impossible to rank issues in a way most people will understand.

No. You have to be a Jira or System admin to create projects. Yes, you can limit people to their own projects. You will have to modify the permissions and user memberships so that people are not automatically granted access, but have to be added to the project or group before they can see the projects.

You'll need to use the REST API to attach new versions of the files when updated, then use a simple "display image" macro to display "latest". Your users will still need to refresh the page.

Configure the board, changing the estimation statistic from Story Points to Time tracking.

That tells us you don't have the permission to create projects. You'll need to ask your administrators to either make you an administrator or create the project(s) for you.

I'd have a look at the rest of the library. I am not going to write your code for you (I've not done it before so I have nothing to hand over)

Create project is under the projects menu, not behind the create(issue) button

The only "download" of a workflow in Jira is an export to xml, suitable for using in another Jira system. I assume you don't want to use that in a presentation. Your only option for a diagram is to take a screenshot of one of the views (edit or "show workflow" on the issue view). You'll then need to pad it out with…

The original estimate is stored in the issue table, but the rest are calculated and don't live in the database. Why are you trying to read the database for this? It's the worst possible way to report on Jira data, inefficient, unstable, potentially a performance problem, and often gives you data that you probably don't…

Strat at https://www.atlassian.com/software/jira/guides/expand-jira/automation

There's a load in the library. https://library.adaptavist.com/entity/set-available-options-to-a-multi-select-list might be a good start

You cannot attach any validation to an issue type. You attach validation to a workflow. You attach Behaviours to screens (but REST has not got any). You will need to put validators on the create transition for REST creates to be checked. Edit has no validation beyond what each field can do.

You'll need to read more of the log file to find out what the root of the error is.

The custom field value allows you to define security levels by a selected user or group on the issue. If your user selects a security level limited by a group or user-picker, then that issue will only be visible to that group or user, plus the others defined in the level. Before the level is set, Jira cannot know whether a…

Not for edit actions. Best you can do is put validators on transitions so issues cannot progress with invalid data.

That's because you are able to select a group that you are in, so you might be part of the security level.

No, because Behaviours are mostly done by adding scripts to the page so the browser does the work as it renders the page. REST renders nothing, there's nowhere to run the Behaviour.