Comments
-
I very much doubt that it works, just that they've missed stuff and not seen the fail, but it doesn't matter in Jira as you rightly can't do it. Yes, you can amend the notification scheme to send elsewhere.
-
The fields will move with the issue if the fields are valid for the new project in terms of field context. If they have no context, their content will be removed. If they do have context, the data remains on the issues, but you may still find that the project screens and/or field configuration hide them.
-
Ok, you don't have admin rights, you'll need your admins to look at this for you.
-
It's the application log we should be looking at. <jira home>/logs/atlassian-jira.log
-
In the second one, click to go back to settings, there should be the rest of the project setup stuff there.
-
What validators and post-functions do you have on the failing transition, and can you have a read of the log at the point you try the transition?
-
For the main API, you'd need to be doing stack traces. For REST, you'll need to set up access logging (and bear in mind this won't tell you if the call is from a user's browser while they're in Jira, or some form of automation, or a script etc)
-
It's the first section (top left) in the project admin screen, listing the available issue types. Projects can't not have one.
-
The Pie Chart gadget is coded to only use field types that are known-length lists, so the answer is "use a gadget that can do it". Your use of summary for alert name is broken as far as Jira is concerned. You should probably be using a select list for that, or labels type field - as they're lists rather than free text,…
-
You didn't clean out the database (drop all the tables) before re-installing did you?
-
Ok, we'll have to check the detail of why manually. * What does the board filter say exactly? * What does the workflow scheme for the project say? * What does your workflow look like? * Can you edit the workflow and remove all post-functions other than the standard 5, all conditions and all validators (you won't be using…
-
You can't - a field is a field, not a variable length array of fields. You'd need to add five sets of cascading selects for this, separately, and allowing for some/all of them to be left blank
-
Ah, right. It's useless in Pie Charts. The summary is free text, so using it in a pie chart will just give you a pie with X slices all the same size - 1.
-
No, no mistake. Sub-tasks do not have estimates placed on them because they're irrelevant. You commit to doing stories in Scrum, and when ending the sprint, a story is either done, or it is not.
-
You'll need to find or write an add-on to do that. And bear in mind that adding up the time on sub-tasks is irrelevant to a sprint.
-
It depends on what you're trying to do. My mention of code was just to say that "yes summary can be used". I think you need to define "add this field to use in a gadget". What are you trying to achieve and where?
-
Have you got Portfolio installed and licenced?
-
You don't. The plugins for Cloud and Server are very very different things, as the products are different.
-
Could you check the project's "issue type scheme" - how many issue types are in there and what's the split between standard and sub-task types?
-
Core provides the main (business) functions - issues, users, projects, fields, workflow and a framework for add-ons and applications. Software sits on top of core providing the Scrum/Kanban/Agile boards. It layers more functionality and a little bit of data over Core projects, fields, workflows etc. Service Desk sits on…
-
I've hoofed it out of the bin. The bots aren't perfect at spotting spam, and the champions don't always check the spam traps very fast.
-
Yes, that's correct. You can not change the full name of an account that does not belong to you.
-
Yes, I've written gadgets that do that before. Where are you struggling?
-
The screencast does not work, but I am guessing you mean the new layout for Cloud Jira? Which is now the only layout available, and you can not go back.
-
Sorry, there was a problem with Community email and I missed your earlier response. That is the "log work" screen, it is not the issue screen. Your admin needs to add time-tracking to your create and edit screen.
-
A board is a view of a set of issues, it is not a container for them. Your board is selecting issues as per the rule you've given it, check the board filter to see what that says.
-
404 means the server isn't serving up a page at that location. I suspect you've either not set up the network correctly, so that it's not routing you to the right place, or that the service is down. If the service is down, then you need to look at the logs to see why.
-
Where you've used user.name, you probably need user.getUsername() (or possibly user.getDisplayName(), but I think it's the login you want, not the display name)
-
Ok, you've not got empty fields, although filling it with 0 is something you probably didn't want to do, because they're taking up space in the database and remain non-searchable. You've used a text field, so you only have the fuzzy "like" search, and with the 0's being added, you can't use "is empty". Essentially, you…
-
Once you've committed to dealing with an issue in a sprint (i.e. put it in a sprint, and started it), then the issue is part of that sprint. If you don't complete it, and it goes into the next sprint or backlog, it still belonged to that sprint, even though you're going to put it into another sprint. It will appear in the…