Comments
-
A virtually identical question was asked a few days ago, although it seems to have been deleted, along with the answers. From memory: * You have too many fields, it's a bad config * The list is scrollable, although it does only go to 25 (25 status fields - broken) * Every field you add to the navigator shortens the list,…in I want to show the field called "Status" but when I type that in to search, many fields containing the word status are showing, and it says 19 more options, continue to type to refine further, but there's nothing to refine, the field I want is "Statu Comment by Nic Brough -Adaptavist- October 2016
-
If it's "done", please accept the correct answer, or tell us how you fixed it.
-
You can do a lot with issue security, but that would mean doing things like * Having different issue types for status reports, and/or * having automatic scripts to decide what security level an issue falls into
-
Not really - that needs "field level security", which Jira does not do. See https://jira.atlassian.com/browse/JRA-1330 for request, discussion and workarounds. (To save you a bit of a trek through that, https://plugins.atlassian.com/plugin/details/23216 might be worth a look too!)
-
It's not as painful as you might think. Atlassian will give you an export when you're ready to move, and that will include everything, fields, issues, workflows, users and so-on. The only things that I've run into that cause significant problems are * If you're changing user management during the move (OnDemand will give…
-
Yes. Two additional pieces of information which may help you understand my thinking * I am not a Panda bear * I actually prefer Jenkins (Hudson) - it has a cleaner interface for the end-user, feels faster, and more easy to set up (as both an admin and a developer setting up CI). However, that's a close thing. Jenkins and…
-
My instinct is still to tell you not to bother. If you're writing in dev for eventual production use, you should be using the target database.But, if you insist on wasting your time, I think you can do it by following the instructions for mysql, but replacing the mysql driver class with "org.hsqldb.jdbcDriver" and the url…
-
I'm not sure that HSQL provides a datasource that can be used by Tomcat. However, I would not bother looking further. You should not be using HSQL for anything other than a bit of development or testing. If you're in dev/test and trying to get the SQL macro to work, that's fine, but irrelevant because when you move to…
-
Yes, volume here is a known issue, I was talking to Atlassian about doing something about it at Summit last week. Your licence entitles you to use any version released before it expires, so you can jump to any version you want at the moment. I would probably upgrade JIRA to 6.4.4, then 7.2, bearing in mind there are…
-
What does the log file say when you try to add the user to the group?
-
Admin rights give you admin rights. Not "everything", and it's not relevant when we're talking about sharing filters. You DO have the right to set columns on any filter that you own. You won't get it on filters that belong to other people. You can only set the column order when you open a filter in the issue navigator, you…
-
You can use "tools -> set columns for this filter" on saved filters. When people visit the shared filter, they'll get your columns at first (they can opt to swap to their own if they want, but that won't alter what you've set)
-
Siddheshwar - the documentation tells you how to use that command in the CLI. It's the first line on https://bobswift.atlassian.net/wiki/display/JCLI/Documentation
-
Yes it is. If you need more information, you'll need to tell us more about what you are doing. You haven't really given us much to work with here.
-
Yup, my third line is essentially that - you are doing it by hand at the moment, but a listener could be written to do it automatically.
-
You can't. A transition has a single end-point, so no matter what you do, "create" always lands on one status. That's it. Your options: * If the different status are for different issue types, create different workflows for them * Write a new "create" process * Include a transtion from the first status to the second in the…
-
Jira does not do mandatory fields on screens. The field configuration tells it what fields are mandatory on the whole life of an issue. So if a field is mandatory, it's mandatory on create, edit, every transition and so-on. It does not care if the issue is not on a screen, if it's mandatory, it's mandatory. There is, of…
-
Depends on how you've installed it. You should consult the documentation for your version, or the team that maintain the server.
-
It's a problem with your network. https://confluence.atlassian.com/display/JIRA/Surviving+Connection+Closures might help improve Jira's response to the fault, but you probably need to talk to your network engineers and DBAs to find out why the connection is being lost.
-
Ok, and which version of Jira? It matters because the user handling changed between 2 and 3, and 4.2 and 4.3
-
What user directory are you using? Are you sure your database is the right one? Are you looking in the right tables for your version of Jira?
-
What user directory are you using? Are you sure your database is the right one? Are you looming in the right tables for your version of Jira?
-
As you suspect, you need to open up the space, then secure the pages you want to be hidden. A trick I've used in a few places - move the "public" pages to another space which is deliberately completely open, and then, where the pages should appear inside a private space, pull in the public one using {include public:mypage}
-
Yes, this is a long-standing bug in Jira - once you've configured one project context, it drops off the list. That's fine if you're only configuring by project, but if you're trying to do project and issue type, it can become a problem. I don't seem to have the bug report bookmarked, but I don't remember that there are any…
-
Remove the field from the "edit" screen, and create if you need to. Put it on a new screen. Create a workflow transition from "execution" back to "execution" and use the new screen as the "transition screen". You can then limit who can use it as well as stop it being edited unless in execution. Or use the…
-
https://answers.atlassian.com/questions/55665/deny-issue-creation-of-a-defined-subtype
-
No. You need to do it manually (use bulk-edit though, it's much faster than one-at-a-time) You might also want to skip it completely - don't delete the user, just remove them from all groups and roles. You'll have a nice neat historical record and the account won't take up any licenses if they're not in any groups/
-
No. JIRA is an issue tracker, it focusses on the issue at all times, and the implicit assumption is that an issue is self-contained. Information shared by many issues probably needs to be shared at a different level - project or component for example. Of course, there's loads of options - some (definitely not all) are: *…
-
What link? And what does "not working" mean in detail?