Comments
-
If you've started a sprint, then this is doing the right thing - moving issues in and out of an active sprint is scope change, so it's recording it. You should avoid doing that, as it messes up what you've planned.
-
It depends on the Theme. You can choose different themes for different spaces (e.g. space1 has default and space2 has documentation). But Themes have global settings that affect all spaces using that Theme, and some of them have local settings that you can amend in space admin.
-
Well, your pom looks fine. It should be already pulling in all the basic dependencies that you need, and your code will determine the others that you might need to add. (As a random example I walked into yesterday, there's no need to include a javax servlet dependency if you aren't going to use a servlet - removing the…
-
The dependencies are whatever you need to support your code. Have you started with a project skeleton built with the Atlassian Plugin Development kit? That creates a pom which covers most of what you need for most projects, and then you only need to add the odd other one depending on what you try to do in your code.
-
No, you need to read the workflows to work that out.
-
The error message should be telling you more than that. It sounds like you've either got a javascript hack that's breaking something, a broken plugin, or a damaged database. But we can't really tell without more of the error information.
-
I'm a little confused on this one. Confluence clustering was removed in 5.6, so what you're writing about cluster safety numbers and so-on is not relevant. Could you clarify - are you using Confluence (single node) or Confluence Data Centre?
-
To do it with javascript, you're going to need to issue a string of commands to the server, over REST. Get the attachment you need, and download it, delete it from the current issue and attach it to the target one.
-
Would it be easier to have dedicated fields for the questions instead of trying to mandate people answering them in a non-dedicated essay field? JIRA supports that very easily - one field per question, and you can use the standard Screens/Field context/Field Configuration functions to only display them in the relevant…
-
You should use which ever your organisation is most familiar with to be fair. I'd always choose CentOS over Windows myself, because it's better supported, far easier to configure and maintain, cheaper, faster and more stable. I've never had significant OS related problems running Atlassian software on Unix based machines,…
-
Mmm. I don't think this makes a lot of sense. A six year old posting about server setup is not right for a recent Cloud system. Whatever you're doing on the SVN side is not connecting to your JIRA correctly. Either you've given it the wrong credentials (although the error message does not suggest that), or it's using the…
-
Transition screens are intended specifically to gather more information from the user during a transition. There's no "display only" option on them.
-
Most add-ons provide functions globally, and only a small handful of them have user-restricted features (but those don't affect the licences you need for them, and they're specifically part of the add-on) The Enhancer add-on, assuming it's the one I'm thinking of, adds functions that are global and it wouldn't make sense…
-
That's what we said already
-
Sorry, yes, should have said add/edit The coffee was not strong here either.
-
Edit
-
You've answered your own question: Group B only has view permission Restrictions do not grant more rights, they limit the existing ones.
-
Look at the "issue type screen scheme" for the project. It lists the three screens (which can be shared) for Create, Edit and View. You need separate screens for Create and View - I'd copy the screen you're currently using for create, and add your field to the new screen and associate that screen with "view"
-
It is possible only with SQL hacks (not recommended). Deleting the issue is the right approach - it will remove it (and the history) completely. Although I'd create the new version first, so you can copy and past what you need from the one you're going to scrub.
-
I think this is a very fuzzy request, because there's no definition of how we know what issues to display.I'd probably watch the issues first (with a filter like "my watches and unresolved"), then go with a label second, and then filter for "key in" third. There's plenty of other options, but everything comes back to "how…
-
You're on the right track. It's not necessarily as simple as "JIRA users". You need to remove them from any group which lets them log in. If you check Admin -> global permissions, you will see that lists "Users", "JIRA admins" and "System admins". Usually, "Users" = "JIRA users", but not always, so it's worth checking. All…
-
This sounds like someone started JIRA as "root" rather than the correct JIRA user, then stopped it, then you restarted it with the correct JIRA user. It breaks because the first run by root took ownership of a lot of the files and hence the JIRA user can't function properly. You've hit on almost the right fix - stop JIRA…
-
Check that the JIRA Suite utilities addon is installed and the transition tab module is enabled.
-
I suspect you need to talk to OnDemand support about this. We can't see your OnDemand settings, and we don't know the details of how OnDemand works.
-
We're end-users of JIRA software, not your system administrators. We can try to help with problems in general, but you need to talk to the people who run your JIRA about access to it.
-
If you take JIRA + Agile + Portfolio, then the answer is "not much"
-
It's not so much JQL or the search that doesn't support this, it's a matter of display. JQL finds issues, it doesn't say anything about what is displayed. The view screens determine what you see on-screen, and they do it with a combination of code to display the screen and code for each field that tells it how to display.…
-
The dialog box I get has a "browse" option above the url one. What version of JIRA are you on?
-
That sounds like it's permissions. Have a look at the permission scheme for the projects, and look at the line that says "create issue". Then check your account matches at least one of the rules in there Note that being an admin doesn't give you any "can do anything" permissions, as that's a terrible security model - you…
-
In my experience (and having had colleagues dig through the code), Jobin is exactly right - there is no "order" to listeners and events. Listeners listen, events get fired, and whichever listener happens to pick it up first runs first. I've boiled this down to the assumptions that * Never try to amend an issue with more…