Comments
-
The API you are using is the REST API - see https://developer.atlassian.com/server/jira/platform/rest-apis/ for the definition. However, I don't think there's much (if anything) wrong with your code. The problem is that you're trying to use a transition that isn't there.
-
Yes, but the best option is to * Install Jira 1 * Change the port for Jira 1 * Install Jira 2 The installers will let you locate the two installations in different places - make sure you specify four totally separate directories (e.g. /opt/jiar-install-1, /opt/jira-data-1, /opt/jira-install-2, /opt/jira-data-2). But they…
-
The end of a trial makes your Confluence go read-only (and be warned, for Cloud, it's going to be deleted within 6 days if memory serves - you get a week to renew or buy before it goes away), so yes, it will fail. Although the error looks different, it may well be a simple "you don't have the rights to do this"
-
Ok, if you have a licence for 10 users but 50 active users, you cannot use the application as you have gone past your user limit. It sounds like the reason this may have happened is that you have accounts that you make active in Confluence and Jira, and you've got shared access. For example, imagine this: * You have a…
-
Your safest option is to look at the "manage add-ons" (or "universal plugin manager" to give it it's real name) from inside Jira, and only use plugins that it says are valid for it. If you can't find an add-on you want, then there is no valid supportable version. You are unsupported if you use add-ons that the UPM does not…
-
I am confused on what you are doing and what you expect here. Let me re-play some of it: You have an issue A. It has a link to issue B. On issue B, you have created a screen that you use when you transition issue B from one status to another. This screen has some custom fields on it, which you ask the user to add to. If I…
-
In what context? It's not a Jira thing by the look of it.
-
Indeed - "cannot reach" suggests a network problem, rather than a server problem, although it is a bit vague. When you talk to your admins, give them the actual behaviour - does it churn and timeout, give you an error message, or a blank screen? etc.
-
To add options to a custom field, you need to be an admin, and you have to do it in the UI (i.e. in a browser) - there's no REST or remote calls for it.
-
Ok, you'll need to do quite a lot of coding in Jira 1. You'll need to write a service to regularly interrogate Pier for new stuff 2. That's rules you'll need to build into the service to ensure the right data is put on the issue to get it to be selected by the right queues 3. Same as 1 4. For simple cases, you can probably…
-
As "your web app should supply the data to Jira", you'll need to define the tl_process field as a label - that's the only field that accepts new content from outside the admin UI.
-
Custom fields do not suggest selections, so I'm guessing you mean you want to edit the list of options available. REST does not yet allow for this, it's aimed at updating issues, not admin.
-
There is no way to do this - if someone has "move" permission in the source project and "create issue" in the target, they can move any issue to any issue type. Move issue is outside the workflow, so you can't use that. Behaviours looks at issue fields in create/edit/view, not structural data during a move. A listener is…
-
You should use the REST API to draw out the data you want. Have a look at https://developer.atlassian.com/server/jira/platform/rest-apis/ to get started There's no way to grab "boards" though, as they're an interpreted view of a data set. You'll need to replicate the queries behind them.
-
From Access, I'd say your most simple option is to export it to CSV and import that. It's likely that you don't need a lot more than that. If you do, I'd look for a local solution partner - https://partnerdirectory.atlassian.com/
-
You also mention "bitbucket" - you can find the same for that by searching for "Bitbucket release notes"
-
No, Atlassian removed the system information because you don't need this sort of stuff on a managed service. The database statistics are also not going to be that useful - Jira Cloud and Server have been diverging for a while, and although number of issues is not a bad measure, a lot of the other stats you've listed may…
-
Confluence doesn't have "custom fields", so your question needs expanding to tell us what you're really asking about?
-
You're going to need to read the various administration screens for this data. However, I have to ask why? One reason for using a "managed service" like Cloud is that you don't want to care about these numbers.
-
Please, do make yourself familiar with the documentation - both of your questions are simple and covered by standard docs you can find a lot faster by using a search engine direct instead of using us to do it for you. For the second, see https://confluence.atlassian.com/display/ADMINJIRASERVER/Supported+platforms
-
No, there's no replace. This is because Jira does not expect you to be using groups in permissions - roles are far more flexible and easier to maintain.
-
You'll need to get in touch with Ominture/Adobe for this really, the insertion of their script renders your Jira unsupported by Atlassian, and they've given you a script that does not work for the current version.
-
Go to the downloads and follow the "all versions" link under the main box to get to the "archives"
-
I would tend to if parts of the work can be done in parallel, but I'd avoid putting estimates on sub-tasks if you're going to do Scrum, because that doesn't work.
-
The best you can do with SQL is a negative search. Get a list of issues that do exist, look for "holes" in the numbers, check any numbers that are missing against the moved issues, and if you are missing there, you know they've been deleted. You could also check the audit log, but bear in mind that can be turned off, and…
-
Your assumption is correct - Confluence doesn't care what you're attaching, it just versions each file you send it. If you have files with different names, you get different attachments. When you give it files of the same name, it simply creates version n + 1. However, I'd be tempted to import the document instead. That…
-
Without a backup, I'm afraid there's nothing you can do - the issues are gone. Atlassian do keep backups, but these are for disaster recovery and aren't suitable for restoring issues.
-
Create a board that only includes the issue type you want. The burndown on that board will show only that type.
-
You can't go back I'm afraid. To get off the roundabout, you'll have to migrate to a server installation.
-
You can, if you have a backup and a LOT of time - you'll need to restore the backup into a Server environment so you can read the issue, then work out a way to "merge" it back into the system from which you deleted it (which can be very complex, depending on how much data you want to restore)