Comments
-
REST was introduced in version 4.0 when gadgets arrived (actually, you could make it work in 3.later if you tried hard) However, the option is listed under something like "Enable remote access via xml / xml-rpc". Can't remember the exact phrase for 4.x, sorry
-
Use the REST interface to create (and update) the issue in Jira from your other tool. You don't need any plugins to use REST, just make sure it's enabled in your general configuration in Jira. https://docs.atlassian.com/jira/REST/latest/
-
You don't need a plugin. Jira exposes a REST interface. If you're writing a plugin, then you probably want to read https://developer.atlassian.com/display/JIRADEV/JIRA+Plugin+Guideand then mark Boris's answer right.
-
I'm afraid I don't understand the question. Jira misc calculated fields calculates some information based on other data and is an addon. You're asking about editing field data, so you need to be doing that in your own plugin, not trying to hack jira misc calculated fields (and, you don't want to edit calculated values…
-
Same way you put in the view templates - lines in the atlassian-plugin.xml that point to them.
-
No problem, I worked it out when I first used the message fields in the Jira toolkit - logically, they had to display on edit screens somehow. But yes, they've got the same problem as inline-edit because they won't refresh on editing oter fields, so it's not entirely ideal, but hey - close is good :-)
-
You've always been able to stick calculated fields on transition screens. There's no trick to it, they work the same as other custom fields - if they have an edit template (obviously without any actual input), they'll appear on edit type screens.
-
Derived or calculated fields can do part of this - you can write plugins that provide them, or implement them with the script runner. They will still not work with inline edit though - they need to be re-read and that means a refresh of the screen.
-
You'll need to look further back in the log to see what is going wrong.
-
I'm afraid not. Atlassian are looking at delegating admin rights, but at the moment, only admins can create projects.
-
I thin the "valid" licence just means that your key is for the right add-on and would work. The expiry date means that you don't have the right to use the add-on with that licence now. You'll need to renew it to get it to work again.
-
The "manage add-ons" section in admin should tell you what type of licences you had. You should be able to renew them from your "my atlassian" account.
-
* Yes. Just create and share two boards * Go to the bottom of the list. Click the last item so it is selected. Scroll to the topof the list and use shift-click to select the whole lot. Then drag into the sprint.
-
Ok, considering part of a failover system without looking at the whole isn't really going to help. For the LDAP, you'll want something that can mirror the same LDAP accounts you're using and provide that to JIRA if it fails. Then for JIRA, have a look through…
-
A system architecture diagram is a little vague as a requirement - what do you expect it to tell you? When deploying JIRA, you need a server to run it, network access to the server, some storage for the installation and data directories and a database to connect to. That's a diagram with one or two simple circles if you…
-
You don't need to have a separate project, just have a board that shows issues in the status each team is interested in and not the ones they don't care about.
-
Let's start with the flawed assumption in the question. Issues do not "move" between boards. Boards select issues based on the data on the issues. This actually makes the solution for your case very simple. You set up one board holding some of the steps in the workflow, and another board with other steps. Let's say you…
-
No. The field is deliberately built to set a resolution, forcing the user to select something. (Also, it's not "mandatory" in JIRA-speak. It's optional, otherwise you would have to set it on "create")
-
You've got two basic routes to doing imports from other system. The first is to write an external program or script that can poke the data into JIRA over REST. (Some people would argue that you could do this via SQL as well, but all I have to say to that is "don't", as you will break stuff and it's a lot harder than REST).…
-
I wouldn't rely on that - it could create incompatible data as you're lying about the versions and potentially throwing complete misinformation at a server. If I were to use that, I'd be very worried, unless I tested at least every macro and function that had been used anywhere in the data, with every combination of…
-
Severity is just a custom field, and you've probably selected a "select list" for it. Try using a "cascading select list" instead.
-
No. Time tracking is a global flag. But... Set up two permission schemes and two sets of screens for the projects. One pair of schemes should be for New products projects: * screens should not include any fields with time tracking or estimates * permissions should not allow "log work" to anyone The other pair should be for…
-
Hmm. Well, I'd probably be tempted to ask for help from the vendor. Although, you could just add the "links" field to youre create/edit/transition screens - that allows you to select issues for a full proper internal two-way link. Think it arrived in 6.1
-
I think your base url might be set incorrectly in general administration, could you check what it is set to?
-
The data integrity check will NOT find orphaned records and even if you think "it's all working now", that could easily be an incorrect assumption. You might be lucky. You might not. I'd keep your backups from before you botched this, you may need them.
-
You've missed several tables. Please, go back to your backup, and use the API to do the deletes. Messing around in the database when you don't know what you are doing is NOT a clever thing to do.
-
Ok, so that means you can dump the backup too (if it goes wrong, you can re-clone). You are not going to get around the fact that the SQL is complex - you need a whole swathe of deletes to get there, and although this is going to run faster than clicking "delete project", you still need to reindex afterwards. It's still…
-
I'm not that familiar with the structure of the database in 5.2, but I don't think it's changed much. The list of core tables you'll need to amend is right. More importantly, you need to understand that although "using http and API takes a few hours", doing it via SQL is probably going to take longer. A lot longer. The…
-
This varies by version of Jira, so we can't give you the raw SQL. I'd also consider alternatives to SQL * Frankly, leaving the UI to churn through is a good option - safe, supported and simple * I wrote a SOAP script that pulled a filter and issued mass issue deletes in batches. Throttled so it deleted one issue a second…
-
You can't free up licences by deleting inactive users. Once you put the "inactive" flag on a user, that's when they stop counting towards the licence - you don't need to delete them.