Comments
-
Mmm, that's not what we're seeing in large corporates. Monolithic documentation is increasingly being seen as pointless, as it's obsolete almost before as it's finished, and it simply doesn't keep up with development and enhancement cycles, let alone supporting increasingly clever (i.e. complex) software and systems.…
-
Depends on the type of documentation. If you need static, fixed, distributable documentation (technical manuals, standardised how-to guides, book like things), then it's not great. If you want dynamic, updated, fast moving and relevant documentation with instant "publication" (i.e. see this web page), then it's ideal. I…
-
Define what you mean by slow, and work out the reasons. Is it your machine, your internal network, your connection to the server if it's not inside your network, the load on the server, or something else?
-
You'll need to do some analysis to work out why.
-
There is no easy way to do this. You can backup everything and then use "project import" to pull in a single project, but you have to do all the configuration by hand to do that. Have a look through the marketplace for add-ons though - I'm not aware of any that will do this as described, but there are lots that can help -…
-
It's a function of the workflow they have designed. You can design your own and include an escalation step if you need it
-
Yes, a screen is a list of fields that would appear *if* every field was global. If you hide fields with field configuration or limit them to certain projects/issue-types, then Jira will discard them before showing them to the user. This lets you do things like "have a single issue creation screen for all projects, but…
-
If a field has the right context to appear, and is not hidden in the field configurations, then it will appear on your screen. If it is hidden OR does not have the right context (i.e. doesn't belong to the project and/or issue-type) then it will simply not be drawn at all.
-
No, I'm afraid not. That's why you've found people using the last resort of javascript (believe me, with Atlassian products, javascript should only be used when you can't do it any other way)
-
As usual, I'd expect the log file to tell you why the re-install from upload has not worked. What does that say when you try the upload?
-
There's no way to pre-select a user like that, but you can use post-functions to set assignees, and you might what to have a look at "component lead" as well - https://confluence.atlassian.com/display/JIRA/Defining+a+Component
-
Set up the workflow to have a "resolve -> Done" transition, then write a filter that says "status = resolved < -5d", then use a jelly escalation script to trigger the close transition. See https://confluence.atlassian.com/display/JIRA/Jelly+Escalation
-
I don't know what you mean by "type of workflow". A workflow is a workflow, they don't have "types".What I was trying to point out was simply that you will need to duplicate data from one system to another (probably as part of a workflow) if you build the solution I've suggested.
-
No. Service Desk is an addon that hooks deep into JIRA. Even if it didn't have deep hooks, it's still an Addon for JIRA - it runs entirely within JIRA. The closest you could get is to have two JIRA systems - an external one with Service Desk and a workflow that has the ability to update duplicated data in your internal one.
-
Edit the properties file as detailed at https://confluence.atlassian.com/display/JIRAKB/How+to+edit+the+jira-config.properties+file and https://confluence.atlassian.com/display/JIRA/Advanced+JIRA+Configuration - you need to look for the "opsbar" properties in the jpm file to copy into jira-config.properties
-
Have a look at https://developer.atlassian.com/jiradev/jira-platform/other/tutorial-adding-menu-items-to-jira
-
Lenny, this post is out of context - we have no idea what problem you thing you are trying to solve. On top of that, a Jira server.xml often doesn't need to be modified. I've been using Jira for a very long time and I've only messed with the server.xml to meet very very specific requirements (and those have all been to…
-
The solution is to use the system as designed. Remove the resolution value of "none", it's not very helpful and it's making Jira behave as though there is a resolution set. I'd question why you think you want to add this value.
-
It's harmless to delete it (just jot down the fields that it had on it so you can put it back if you need it). The screens really are just lists of fields to present to a user at certain points (tabbed or not), so deleting a tab does not actually change any data.
-
You'll have to delete it - not much point in having the option to have it if you can hide it - might as well delete!
-
Run a filter for "past due date" and "assignee = current user" then subscribe jira-users to it. Be aware that you are going to get complaints about doing this - people really don't like having reports like that forced on thm.
-
No, not "create", you need to use "create sub task", which is under the tools menu on the issue (far right hand side of the issue view screen) You can't edit the issue type to convert it to a sub-task either, and there are no other issue types in your project that are compatible, so you can't "edit" the type at all.
-
I suspect you are using "create issue". You can't create subtasks from there, you need to go to the issue that you want to make them a sub-task of. Use the tools menu to create one, then the section will appear and offer you the + option to add further ones.
-
Yes, there's a section for this in Admin. Do you have a a question about it?
-
Yes, it's a restricted function on Cloud. You can't disable the add-on.
-
Ah, ok. You need to contact Atlassian support to get an export of your OnDemand data. Once you have that, you'll be able to import it into your new server (Assuming the version of Jira you've got is the same, or higher, than OnDemand), copy the attachments, and it should work fine.
-
The answer to your first question is a simple "yes". With the caveat that your new Jira server must be the same version of Jira, or *higher* than your old server. For "how", there's actually quite a number of ways to do this. The best one depends on exactly what your setup is. What is the old server basically? Yours,…
-
The bus I get doesn't have security levels.
-
Yes, I was sort of trying to eliminate the two-directories with the "duplicate user" questions, but I'm not that familiar with LDAP problems with directories, because I've mostly only worked with "flat" LDAP (single directory) hookups. I still think it could be the root of the problem, but I've reached the limit of my LDAP…
-
Not a problem. It's actually a really good example of how a question should be worked through. Even though I couldn't work out what the heck is wrong (and am really annoyed, especially because I've a horrid feeling it's going to be something simple that I really should have spotted immediately!) You've started with a clear…