Comments
-
You can't. The logic is quite simple - there's no need to see sub-tasks in the backlog. You prioritise (i.e. shift the backlog around) at a story level. By definition, if you have subtasks on a lower priority story, they cannot be more important than the subtasks on a higher level story. As you don't need to prioritise…
-
What do you mean by "encrypted"? JIRA does not encypt attachments (unless you've got an add-on that does it), so do you mean the disk is encrypted?
-
The link in the Answer I gave earlier is still valid. I'd like to add that if you have a medium sized or above Jira (>100k issues, or a decent swathe of users), then it's worth avoiding a direct connection - your backup or failover solution should really involve database replication, and you should be looking to use a…
-
You probably need to start with http://confluence.atlassian.com/display/JIRA/Database+Schema
-
It cannot find your class or possibly .vm that the xml refers to, or possibly something that you've relied on in the plugin compilation that isn't in the Jira structure. Check their locations in your plugin directory structure. To track it down: Are there any warnings when you compiled the plugin? Read the log for Jira…
-
Backups need to be of the same version of JIRA to do the import safely, although there some fixes/workarounds Could you tell us exactly what the two version of JIRA are?
-
You should also reverse out the SQL changes you made to restore functionality before you do anything else.
-
Could you please stop tagging things with "on demand" when you are NOT using OnDemand? Anyway, yes, you should never update a Jira database with SQL unless you know exactly what you are doing. You probably have neglected to update the counter table sequence_value_item Also, if you are going to use SQL on a Jira database,…
-
Um, don't give the pages the same name? We leave the page names blank so the users have to fill them in.
-
Not really. There's certainly nothing to generate it in JIRA, and the setting of the announcement banner is something the administrators do manually. It is stored in the database, which you can't update while JIRA is running and you don't have any access to in Cloud anyway. So you'd need a remote call to do it, but that…
-
A condition to do that might be quite simple, but there's some missing behavioural rules here. "Make sure the number of attachments has increased by 1" is part of the definition, but we need the rest. Specifically "since when"? Last edit? Last transition? Since it arrived in this status? Since last week?
-
You also need to work out how they got deleted, and think about preventing that in the long run.
-
That error means that the Confluence server cannot reach the other server. Either the tableau server is not running, it's not accepting connections, or most likely, it's firewalled off. I'm afraid you'll need to debug your network connectivity to fix this one.
-
My guess was that "Task" is not an issue type in the target project.
-
There's not enough information to tell what you're trying to do or where here. What is your code trying to do and where are you running it? Plugin? Gadget? Etc?
-
The request for priority schemes is around 12 years old and not a priority for Atlassian, although they have not said "no". See, watch and vote on https://jira.atlassian.com/browse/JRA-3821
-
I'm afraid you can't. JIRA's priority list is global across all projects. There are some tricks you can play with javascript or add-ons that remove options from the list, but they're all less than ideal (easily bypassed and not working in all the places you could set it). The other option is to hide priority and use your…
-
See https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email The standard handlers have a simple rule - if the summary has a Jira issue in it, then it's a comment on that issue. Otherwise, it will be created in the default project configured in the handler. If you want something more complex or…
-
Correct - an issue that has anything at all in the resolution field is considered to be resolved by Jira. It sounds like someone got very muddled up here. The resolution field should NOT be on any "create issue" screen unless the intention really is to create issues that are resolved immediately (this is valid sometimes,…
-
Ah, now that narrows it down to one of two problems. First one is easy - a broken index record for it. To fix that, simply edit the issue. Any change to a field will do, I usually add a full-stop to a sentence in the description or summary. You should try this first because it's a very easy fix and needs to be ruled out as…
-
Ok. Can you do two things now * As hinted before, go to the issue view of video-4210 and look at the area where resolution normally appears. What exactly do you get for the resolution (or confirm that it does not appear at all) * Look at your search - is video-4210 struck out?
-
I'm not sure why you are using two "unresolved"?
-
Three possibilities * Your filter is not doing what you expect because you're misunderstanding how they work (there are a few quirks that make them less than intuitive sometimes) * Your filter is referring to data that is doing something odd * Your index is broken To debug all those cases, could you tell us exactly what…
-
I think you are misunderstanding how user directories work. I'm sorry, I've been misunderstanding the question as well, as I focussed on the LDAP settings and forgot to think about what you *might* be asking, for which I apologise.LDAP provides Confluence with users and the groups they are in. It doesn't care what…
-
I can't tell you how your LDAP is set up or how to configure something to connect to it. What is the server name? What's the user you're going to connect with? What CN/DN are you going to use? If you want me to tell you those, then you'll have to tell me what they are. Then I can respond with exactly the same information…
-
>I would like to create a group(e.g Group A) in the LDAP directory and only the users in that group should be allowed to access JIRA during login. This bit is easy - go to global permissions and put group A into the "JIRA users" permission so that they can log in. After you have that working, remove the other groups in…
-
At a guess, you have not applied the field configuration scheme to the project.
-
No, JIRA is licenced in tiers, and they start at 10. To do this job, you need to have an account on the system you are going to be working in - you'll need to consume one of the 10 (or 25, or 50, or 100... seats they have)
-
You are confusing "permission" with "type of person who can do it". As I said, try clicking "add" on the "browse" permission line.
-
Look for "Reporter (show only projects with create permission)" after clicking "add" on the main screen of the permission scheme. If it doesn't appear, check the changes you've made in the file and that there's no errors when you restart jira.