Comments
-
Ok, my guess was wrong, but your question was originally only one line and no explanation at all. Your edits have helped I think, but I would like to confirm what you are seeing: * We go to create issue * We add an attachment on the screen * We fill in some fields, but we miss one of the required fields (e.g. summary) * We…
-
That's not really any form of question, and is a bit sparse on context. I can try to guess: Do you mean "Is there a way to delete the attachments if a field is empty?" If you do, then the answer is "code" - you'll need to find/write a post-function or listener that can delete the attachments. Also, you may note I dropped…
-
I know it used to let you do that in the past (barring "summary", which is always required), but some of the importers have a bit more respect for the config nowadays, and I've not tried the CSV one recently. However, I think the new version does, as you suggest, execute the validators on create. I should have said that in…
-
This implies that you have a field called "originating version", you have made it mandatory in your project, and you are now trying to import CSV without that field set in it. Either (temporarily) make the field optional, or place a column into your CSV and map that one. That's just for a test to check that I've got the…
-
Yes, but you need to read the change history to find it - iterate over that looking for "your field" and oldvalue/newvalue
-
Not natively. Alex has pointed you at the built-in handlers, but they will not map issue types, they use the project default or the type set in the handler config, they don't read the email for a type. The advanced email handler, JEMH does support this. Or you could write your own handler (if you're going to try anything…
-
I know. That's what I've been telling you - your user had the wrong access.
-
That doesn't change the fact that your database is broken - the last error message tells you what the problem is - you're missing a table, or access to that table.I'd check the production database, as it suggests that you've now got a broken production enviroment because you've upgraded it by using a user with the wrong…
-
I think you need to take a look at the database - it still looks like you've created a broken test system by using a user who does not have the right access to create and update tables.
-
Erm, well, "we just added an entry into cwd_membership" tells me that you've been messing with the database. That's almost always going to break JIRA unless you have a *complete* understanding of the database structure.The right thing to do here is revert to the backup you took before you ran any SQL updates in the…
-
That's not an error I'd associate with an attempt to log in. When you log into JIRA it reads your user profile, but the error you are seeing is related to the Agile add-on or JIRA Software, nothing to do with login. My best guesses are * You've got some sort of broken Test system (cloned from Production but missing things)…
-
Ok, Jira logs in two places - it looks like you've got the Jira application log there, but in this case, the application server log is probably gonig to be more useful. On the assumption that you're using Tomcat (which is the default recommendation and the one built into standalone/binary Jira) then you need to look for a…
-
You're already in the right area, but you'll need to expand on what you mean by "detailed" to get more guidance
-
I do not get a 404 when using a direct click, opening a new tab, or copy/pasting the url. Google can find it. Please check.
-
No. Project keys are fixed and single. For a lot more detail, see today's question - https://answers.atlassian.com/questions/149570/move-issue-and-don-t-change-the-pkey
-
JIRA hides fields with no value to try to reduce screen clutter - you have to use the full "edit" function to put a value in. Although you could include the field on the transition screen to the next state as well. To set it as a default, you'll need some code - I'd use Behaviours in the Script Runner add-on to do that on…
-
Apologies for getting picky, but I've answered based on the wrong assumption of what someone means by "application server" too many times. What's particularly annoying is I use the term regularly myself without explaining which one I mean. I got caught a while ago when someone taking minutes of a technical meeting pointed…
-
I need to be careful here... When you say "app server"... Do you mean the same physical or virtual server (I mean the hardware - cpu/memory/disk box)? Or do you really mean what you said, the "app server" - Tomcat/Websphere/Jetty etc? If you mean the same physical machine running Jira, Confluence and Stash separately (i.e.…
-
You talk about test cases and categories - that implies you're using some form of test addon. You'll need to see what functions that has. If by categories you mean some custom field you've defined on issues of a type "test case", so it's all really just plain JIRA, then the answer is "JIRA isn't designed for making bulk…
-
There's no quick way to do this. The slow way is to go to "manage addons" in Cloud and look for all the addons that are not "system". That's what you've added, and that's the list you'll need to install on your Server version. You don't need to worry about the hundreds of "system" ones. A few of them go away in Server…
-
No, you don't need any settings.A question though - what does "we failed" mean? What goes wrong?Also, you should upgrade to 5.8 - a lot of work has been done on the mobile html/css/javascript since 4.2 and you would see improvements there.
-
JQL is for finding issues, not users. I'm not sure I can add a lot to that statement. JQL absolutely requires that you phrase the question as "show me issues that match <question>". Not users. If you want to search for users called Bob, then you need to go into the user maanagement and ask that to show you Bob. Nothing to…
-
Nope, there's no way around this. If a field is set to X on an issue, then anyone who can see the issue can see that it's set to X. (Unless you remove the field from all the screens, then no-one can see it's set to X)
-
No. Screens are used by projects and issue types, not users. It's basically the same as fields, just one level up. You can move "edit" functions into the workflow and control that with conditions like "user is in group", but the main Create, Edit and View screens for issues are a function of project and issue type. Nothing…
-
You can't. Jira doesn't have field-level security. You've already found the only half-way decent answer - a plugin that doesn't function on OnDemand. I've seen tricks played with Apache and internal code as well as that plugin, but you have no access to those for OnDemand either.
-
Horizontally represented groups of issues on an Agile board.
-
You could edit the "view" screen to put some/most/all of the custom fields into tabs
-
Nope, that's a layout thing, and you can't change the code doing it on Cloud.
-
I was going to say that I know of several places using Confluence for call-centre related stuff. As Giuliano says though, their exact usage may not be what you need, so it would be better for you to describe what *you* would like from it and see what we can help you with!
-
Just make sure the board includes the subtask types and then try setting the swimlanes to "stories" (You won't see them in planning, because you don't need them there, but they'll appear on the working view of the board)