Nic Brough -Adaptavist- Expert

See https://confluence.atlassian.com/adminjiracloud/adding-editing-and-deleting-an-issue-type-844500747.html Saying "features classification to systems" is very vague, all it tells me is that you want to have some way to distinguish issues from each other. You can do this with fields.

How do you want estimates to work?

You can't just cast an object to an integer and hope the computer can guess what you want it to do. You'll need to unpack transientVars in full and extract the action id from it.

You'll need to describe what you mean by "web ticket" - it's a phrase that could be applied to Jira issues amongst many many other things.

Ok. But you said one account does get mail. That tells me that Jira is able to send the mails. You'll need to debug people's email accounts to find out where the mails are going.

No, you can add more issue types, and rename any you want (just do NOT rename Epic, it breaks some stuff if you do that, although Atlassian are working on getting rid of that problem)

Could you explain why you are posting random bits of error message and what it has to do with Jira?

If you mean you are using issue links to link issues, and not sub-tasks, then yes, this is correct. Linked issues are not child tasks so there's addition (you can't do it anyway - imagine a link like "X relates to Y" - you end up with an infinite loop - time logged on X needs to be added to that on Y, so that new number…

Bear in mind that if the system is configured to send email to a set of people, and one person in the set gets the email and another does not, then the problem is not with Jira. It is sending the emails to everyone in that set (except maybe the person who triggered it, if they have "email me on my own changes" turned off).…

Are you using the right version of Java for the version of Confluence? What have you configured differently to what the installation docs tell you? What is the rest of the error?

Use an issue type called "feature" and a field to select the system from. You'll then be able to run reports and searches based on "issue type = feature and system in (x, y, z)"

You should use a REST call that is a search for issues, including a call for "and updated > -5h"

You will need to work out how to do that for yourself, I'm not aware of anything that does it already, nor a developer who has done it before.

For server SSO, look to Crowd or apps in the marketplace. There are quite a few in the marketplace, and I don't have your full set of requirements for it, so I can't narrow it down for you.

Use the REST API to interrogate it. As a simple example, look at "show me the issue data". For the most simple of issues (a couple of comments and one custom field), you need at least 30 joins in the statement, and that increases with every field, comment, and change to the issue. Or you can use a single REST call to get…

Your embedding process will need to form some way to log into Confluence.

Software can't fix a human getting confused, or needing to "download before it can be used normally". Could you explain the exact problems you are trying to fix?

If someone can view something, they can download it.

Migrate the data. These two apps store your to-do lists in different ways, they're not looking at standard shared data, they have their own data stores. You'll need to come up with something that reads the data from "My ToDo" and writes it back into Smart Checklists

The start/stop button from Tempo creates standard time logs. Which, when used on sub-tasks, roll up to their parent as described by Fazila in another thread on this question.

401 means you are not authorised, so you've either given it the wrong credentials or you're not calling the authorisation system correctly.

Yes there is a way sub-task time logs are reflected in the parent issue - it's the area that Fazila has pointed you to. Repeating the question as a comment on an answer that answers it adds nothing to the conversation. Could you please read what Fazila said?

That's not what cascading selects are for. They are intended to help people find a single value from a long list, by breaking down the list into sections. You will need to use a multi-select or check-box field if you want to select many options.

"force a change", no. You can't force any change that is not valid in the target. (Well, actually, you can force it, but that breaks things so badly, you're never going to be able ot recover). Asking an issue in a different project to take a valid move through its workflow when you do something with the current issue -…

Next-gen are an attempt to simplify and increase delegated power for the end-user, they're mostly written from the ground-up. Trying to reduce the reliance on administrators to manage all the schemes is one goal. So, epic success on those terms. Fails on having the power and flexibility that schemes for classic have…

Next-gen projects do not use workflow schemes.

Not quite, because sprints do not belong to projects, and reporting is based on issues, meaning you have to define your reporting by the relationship between issues and projects and issues and sprints. But you can do this. First, create a search that draws in the issues you are interested in. For example "project in (x, y,…

A listener is the wrong place to look. A listener reacts to an event, after the event has happened. The edit or transition is complete by the time a listener gets to look at it, too late for validation - the human has committed the data and the service stored it before the listener gets it. You will need either a validator…

So you do understand that what you were saying earlier is wrong? Good.

Wow, well that's a complete misrepresentation of the other conversation.