Comments
-
Ach, no, ignore me - Bob won't see the issue at all, he's not in A. I think you need to establish an exact pattern for this behaviour. Concentrate on one issue, with one security level and then find two users - one who can see it, and one who can't. Then look at the differences between them. What security levels can they…
-
I'm sorry, I forgot. I have a feeling that you can only see levels of which you are a member. Let us say you have security levels A, B and C You set level A on an issue User Alice is in the groups that are named in A and B, and Bob is in groups that give him B and C. Alice will see level A on the issue because that's what…
-
If it's not there, then the security level has not been set.
-
You will only see the field if you've got a security scheme associated with the project, AND a security level is set on the issue. If it's not showing, then there is nothing set for this issue.
-
JIRA notifies on events, not changes of field. Issue security changes should be sending out "issue updated" events though, so you should be catching them. (Note that it won't email people who can't see the issue)
-
You'd need to write code to read the database directly.
-
Yes, it does. And virtual servers. There is a trick with the disks though - whilst it's fine to put the attachments, plugins and the rest on shared storage, it's worth avoiding it with the index. Most of the files it needs are static, or speed of access is not a critical feature, but for a performant Jira, you really want…
-
I'm afraid Atlassian have (annoyingly) dropped the WAR/EAR distributions that you would normally use for that. I think your only real option is to do one of their installations on a temporary server and then extract all the stuff you need from it to deploy into another Tomcat
-
There's a Karma threshold - when you cross it, someone from Atlassian will contact you and ask for a postal address
-
Yes, I understood perfectly. You said you were able to do it in some projects and not others. That tells me that you have the global permission. Could you re-read the comment and make sure you have understood it. As your last comment implies you have ignored it.
-
Ok, if it's by project, then it's probably permissions or the setup. Check that the comments are enabled as "rich text" fields, and then make sure the users you want to mention have access to browse the issue.
-
What do you mean by "browse users in a project"? Where are you looking?
-
Yes, that's exactly what Jira currently supports. Letting your PMs be Jira administrators is a recipe for complete disaster (except for me, because I've had a lot of work in the past undoing the mess it makes) First, remove your PMs from System and Jira administration, then revise your permission schemes. Specifically,…
-
No, it's an issue tracker. It's got worklogs, as you say, and hence you can report on "time spent on project" But there's no financials in it - you'll need to use add-ons to incorporate and use that sort of data. I'm not sure I'd recommend any specific plugin in the marketplace - I've not used Jira like this really (Well,…
-
Start with https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email
-
That's a code change - you'll need to raise it as a new feature with Atlassian https://jira.atlassian.com/secure/Dashboard.jspa Personally, I'm not sure that sharing is particularly useful to log - it doesn't change the issue, so there's nothing to log there.
-
In Confluence, a page name has to be unique in a given space. So, the short answer is "no" There are some add-ons which allow you to fake duplicate names, sort of, but I don't think any of them support the structures you've defined here - they're aimed at different things. Have a look at Scroll Versions and Viewport (and…
-
Ok, so the mappings are probably ok. That implies your data is missing the fields in some lines you are trying to import. HOwever, as the errors are consistent, I'd check that your sheet doesn't simply have a load of empty lines! For due date, you'll need to add a column for it, or make it optional in the Jira project
-
It's actually quite simple - the project you are trying to import the data into has required fields, and you have not provided those fields. I think you need to take a closer look at the spreadsheet you are importing and make sure it has all the required fields mapped correctly.
-
Sounds like your group membership or roles have been changed. Check the workflow conditions and whether your account still matches those.
-
I can't help you with the volume question, but changing the parent of an issue doesn't involve changing issue type. Go to a sub-task, and "move" it. You'll be asked for project and *parent*. Leave project alone and choose the new parent issue.
-
Ah, I'm terribly sorry, it seems I've misled you. Atlassian appear to have removed that functionality from OnDemand (and Jira 6 in general). I don't know if there's a hidden flag to re-enable it or something - I'd raise this with Atlassian OnDemand support
-
That happens automatically on Jira 4 and above - the first couple of issue types in the scheme appear. What version are you using? (Obviously it's not OnDemand, as that does it)
-
Go to admin -> projects. This is a different list to the "projects" list in the main bar - it gives you all the projects, even when you have no rights to see them, as the admins need to be able to see all the projects admin interfaces (or they can't do their job)
-
If you think other software is better for you, then feel free to use it, instead of wasting your time insulting people. There is a wealth of information on Greenhopper in its documentation, and that documentation is, in my opinion, easy to follow and very comprehensive. Start at…
-
It can't "integrate", it's simply not designed to work with Gitlab, because it's mostly built to do what Gitlab does, but better Ok, I feel like a salesman there. I don't want to. Bitbucket is a direct competitor to Gitlab. It can be better than Gitlab, but it depends on what you want. Gitlab could be better than…
-
If there's a JDBC driver for it that can be installed into a Tomcat, then yes, you can use any database you want. Of course, you won't be supported unless it's one of the four Atlassian do support. I don't believe that there are any plans to support anything other than the current four databases (barring maybe adding Maria…
-
That addon is by a third party, not Atlassian, and it does NOT address the problem reported in the slightest.
-
No, it's a right pain. Atlassian recently finally relented after years of complaints and said they might fix it, but I'm not holding my breath.
-
Yes, and that's why the answer is wrong - you could lose issues from the result because the field is not valid.