Nic Brough -Adaptavist- Expert

Cloud backups are XML. It's only really Jira server or Cloud that can read it usefully, but if you're willing to plough through transforming it, yes, you can.

It is the "if" statement that is checking if the selection is M. Select lists hold "options", not strings, so "if ( <option that is labelled as M> == 'M' )" is going to return a false. I would usually do it this way: if ( "M".equals(tshirtsize.getName() ) ) (I've had defensive coding kicked into me, and the use of .equals…

Better than an actively aggressive one.

"status report" does not tell us anything about the report you want. All I can really do is say you probably want to start with a filter for the issues you want to report on and then take a look at the available dashboard gadgets to see if one can show you the filter results in summary.

It's ugly, but you can put code into the "create issue" transition to block them. If you have ScriptRunner you can do this: https://library.adaptavist.com/entity/restrict-creation-of-certain-issue-types-to-members-of-a-project-role but there are other ways to do the validator. However, it really is ugly for the end-user.…

Ok, so * Outgoing - yes SR can easily make SOAP calls to other systems. * Incoming - not directly. You would need to write an entire SOAP style interaction, and I don't know that you could get it to "listen" the same way XML-RPC does. You might have to provide REST end-points to tell it to listen to the next SOAP message I…

There is a howling bug in the draft workflow editor functionality. You cannot add transitions out of a step/status unless it already has at least one. Atlassian are not going to fix it: * It's suprisingly hard to fix as a bug * It only affects admins when they run into it the first time (you won't do it again, now you…

There are some automation and scripting apps that would enable you to set this up. I know ScriptRunner can do it (as I work for Adaptavist, I've picked up cases where people want such scripts, and then nicked https://library.adaptavist.com/entity/transition-an-issue-using-issue-input-parameters to do most of the work). I…

Um, sorry, the question was about changing status, not finding issues.

They have - it's called "using the right field type" Converting can be a right royal pain though, especially if you have a lot of labels. But you can do the housekeeping while copying the labels into the new field.

I'd agree it's time for Atlassian support. Have you raised it with them yet?

Do you mean call other system's SOAP APIs or implement a SOAP interface in Jira?

Without the request there to hang the external comments on, there's no need to label internal comments as you can't have any external ones. They're just issue comments.

Have you tried any of the "time to response" reporting built into Jira? (Or by apps) That will be easier and can be done without leaving Jira.

Atlassian don't provide "sandpit" systems directly. You can sign up for small free Cloud accounts, but if you want to do Server/DC, you'll have to run up your own installations with "developer" licences (these come with commercial licences, so you can ask your admins for them)

Have a look through https://support.atlassian.com/jira-service-desk-cloud/docs/receive-requests-from-an-email-address/

Not quite. I'm saying people should use "password safes" and when they do, you do not want to turn off auto-complete. If people do not use password safes, you will find they use weak passwords, or write them down in insecure places. Either way, you do not want that to happen. Encourage them to use password safes and do not…

Remove the labels field and add a tag custom field of type "multi-select list". Only admins will be able to add entries to that list.

Do you have any files from the Jira installation's "export" directory? That's where the regular xml backups would be, assuming you have not disabled it (Strongly recommended for medium and large systems which should be done via database backsups) If you have any export files in there, you should be able to restore from…

Everywhere I've been that allows multiple assignees develops significant problems with "I thought someone else was doing it" (and often two people working on the same thing without co-operating). It's a terrible thing to do and it always always fails. By all means, name other people as involved or interested, using group…

Correct, Jira does not put descriptions on the view screen, as it would be even more clutter.

A plugin would have to do the same, if not more, work in rendering it.

Correct, a REST API fetching a request can't do anything if there is no request there. The data will be available from the REST API for the issue though.

No, there's nothing you can do other than simplify the data.

I can't tell you any more than to look at admin -> issues -> custom fields -> <your field> -> edit

This is a horrible way to use a tracker system. Please don't try to demand people fill in separate forms. Ask them for the data in the issue, so they don't have to mess around in excel.

The permission scheme for that project only allows move, comment and delete for the assignee of the issue. Admin rights do not mean "can do everything", they rightly mean "can do admin"

No, you should create the projects (and portals) that you need. Most JSD people will add an organisation for each customer organisation.

Password policies in LDAP apply to people logging into systems via LDAP. The connector to an LDAP service do not password policies applied to them because they are not logging into a system via LDAP, and you usually don't want them to have the policy applied - you don't want things like having your entire estate of servers…

Then why label it confluence and put it in the confluence area?