Comments
-
I think you need to spend some time with the Atlassian documentation. Please have a look at https://confluence.atlassian.com/display/JIRA/JIRA+Documentationand try the search facilities
-
I keep forgetting about that. But I'm working with JIRA systems as far back as 3, and that wasn't in the older ones.
-
And what Mark said too.
-
Go to the marketplace and look for the script runner, using a browser. Look for the "version history" tab. Select the one you want (I'd recommend the latest one that is valid for your JIRA before 4.01 was released) and download it. Log into JIRA, go to the UPM and look for the "upload addon" option, and feed that the…
-
You have an "update custom field" post function on the workflow transition, referring to a field you have deleted.The function is from the jira suite utilities, but it should still show up when you edit the workflowjava.lang.IllegalArgumentException: Unable to find field 'customfield_15854' at…
-
Could you read your log file for a time around the point you get this error? You should find an explicit reference to the custom field number with a load of developer info stuck around it. (Actually, just searching your log for 15854 should turn it up too) The error message should include some class names which would tell…
-
The size is a good indicate, but I'd want to use a "diff" tool to check exactly what changes have been made
-
After you do the import file fix, does the xml still contain all the data? Check with a diff off the before and after files.
-
Deniz has covered it, albeit with a slightly different route than I'd take (same effect in the end) You need a new workflow scheme for your project, one that uses your new workflow. You associate that with your project. That separates it from the other 12 projects, they will be using the old workflow scheme, so you go into…
-
I can never remember the full range of options on Cloud, but I remember some of them ;-)
-
Again, that's not available for Cloud.
-
I'm afraid not, there are no equivalents for Cloud, and no way to make that one work on Cloud either. (Yet, I'll ask the product manager if there's any chance of a "Connect" version) I think the closest you can get is probably "Confluence Questions", which is not really a forum, although it has some similarities. (You're…
-
The addon labels are really handy - the vendors of the addons tend to monitor them, and as Boris says, it's really good to have one single searchable forum for related stuff.
-
JIRA does not have a changeable hierarchy. JIRA Core allows for Project, Issue/Story, Sub-task. (You could argue that Category groups projects and you can use components to break down issues within a project into other groups, but I don't see those as hierarchical) JIRA Software adds Epics to that, converting the issue…
-
This was asked and answered only a few minutes ago. https://answers.atlassian.com/questions/236409/can-i-open-up-confluence-questions-to-anonymous-users-just-like-i-can-do-with-confluence-spaces
-
Ranking and due-dates are different fields. You could add "order by due date" to your board filter, but that removes the ability to rank them.
-
The usual reason for the upload link missing is that you are using Cloud Jira, where you cannot install addons. If your desired addon is available for Cloud, enable it from the Cloud maintenance where you set up the trial, not from within Jira.
-
(oops, sorry) For server version, it'll carry on working, but you won't be supported, and you won't be able to upgrade to any version released after the end of your licence.
-
Cloud Confluence I assume? If so, I suspect that it means you need to pay the bill for the account.
-
In what sense? What is telling you about these losses?
-
Oh, um... Membershipbase has gone too. I think portalpage may have gone since that script was written too, and I don't see any references to the many-to-many table that I keep forgetting the name of. Frankly though, I really wouldn't do it this way - it's a nightmare if there's any chance of getting any of it wrong (to the…
-
Userbase was deprecated in Jira 4.3 - the system moved to an internal embedded Crowd. See cwd_user instead.
-
I'm sorry, that makes no sense.Alice is correct in saying that it's a really bad idea to change the ID of fields, it's a nightmare. What you should do is update the groovy scripts to use the new ID
-
It's a simple summary of the project. It gets hidden if there is no information for it to display. From memory, I suspect you've hidden "components" and "affects versions" in the field configuration for that project. Try enabling them (temporarily) and see if the panel re-appears.
-
You'll need to give us more detail if you want anything from us. (There's a temptatation to say "look at the css", but nothing more because there's no question here)
-
Yes. If you have 2000 users in both Jira systems, you need a licence for each system, at 2000.
-
Ah, true, the audit log is an adaptation of an add-on that was written for JIRA 4, and is only included in 6.something and above (I want to say 6.1, but don't quote me!)
-
Well, there's no "project group" concept in JIRA, so I assume you just mean "groups". Group changes are not logged by default, so you won't find anything really. But if you turn on the Admin Audit Log, you'll begin to capture group changes, so you'll be able to look in there for it from then on.
-
Look at the status of the issue and what the "done" column contains on the board(s) the sprint belongs to. What are they?
-
There's a line in the .vm files those docs refer to that is expanding the text from the issue. Probably something like $issue.url Remove that, or swap it to something like $issue.key and it'll go away