Comments
-
Glad to help! "Manage add-ons" and then looking for the upgrades flag is always something worth doing when you have a problem with an Atlassian application. Something I wish the docs yelled about a lot instead of quietly mentioning it here and there.
-
Ok, we'll need to see more of the error message - the java.lang.reflect.blahblahblah should have a lot more text around it, lots of lines of "caused by"
-
Mmm, there are a lot more answers than an advert, and it depends on what formats you need, how you want to use it, and how you want to give it to the users.
-
That resolution thing has to be one of the top three subjects of jive/osqa/answers/community since JIRA 2.0 was released!
-
The board types don't matter here. Board 1 selects a load of issues and allows the users to work with them in either Scrum or Kanban ways, depending on the board type, and board 2 does the same independently. They both act on the selection they make from the underlying list of isssues, so changes in one affects what the…
-
For most fields to appear on a view screen, you need to ensure they have data in them For an edit screen, they always appear if you have put them on the edit screen (admin -> issues -> screens -> screen used for edit).
-
What does this have to do with Atlassian applications? If you're using some dubious program to botch hacks into an Atlassian application's UI, the simple answer really is just "don't"
-
No, JIRA does not have "field level security" that would allow you to prevent specific fields from changing.
-
>move issues to a different board No, because that's an incorrect assumption about how it works. Boards do not contain issues. Projects contain issues. Boards show you a view of a set of issues. What you want to do is set up the boards so that when an issue reaches a point in its lifecycle, one board stops selecting it and…
-
Your target version is now a "custom field", not a system field you can use directly in the standard API. You need to be treating it as a custom field now.
-
Note that the "unresolved" JIRA shows you actually means "there is no value in the field". Some people make the mistake of adding options like "unresolved" to the list, which breaks, because the field is filled in, so the issue is resolved, whatever the option is named.
-
It's in the same place - board config, card colours. You can colour by a range of things, including JQL It is now just a line on the card though, rather than the whole thing.
-
Depends on the field. If it is the "components" field, then they need to ask a project administrator to add it. If it's a "custom select list" (it sounds like one), then they need to ask a JIRA or System administrator to add it.
-
There were some issues in 5 where swapping back to the simple view actually removed some of the complexities the user had added in advanced mode. 6 chooses not to loose them, and is more ready to refuse to swap back when the detail will be lost.
-
You've got one or more lines with an empty value for the column you have mapped to summary.
-
Yes, you can do that in workflow. You want to add a "screen" to the transition from one status to the next, place the log work field on it, and then add a validator to enforce the users entering something in the field.
-
You've got a broken function on the create transition by the look of it. Have a look at the validators and post-functions on the transition and see if any of them might be broken.
-
That's a decision for your organisation and teams, especially those who are going to have to deal with bugs. Generally, what you've got there is a recommended layout for a story, which makes a lot of sense when you're telling the story to the developers. I don't think it makes much sense for bugs, as a bug is usually…
-
Check that you are on the latest version of the Suite Utilities for JIRA. Then go to the workflow and try reconfiguring the post-functions you've used from it on the failing transitions.
-
The linkedIssues function is for linking to issues in the current JIRA. JIRA cannot have any understanding of the issues in other JIRAs because it does not know what might be at the end of a link to a web url. To do what you're asking would require one JIRA to index another one, for which you'd need quite a lot of thought…
-
Check the project permission scheme for who has "browse project". Add them to a group or role that is used in that access rule.
-
For server, go to "find new add-ons", search for it, and download and install it For Cloud, you'll need to raise a request with https://support.atlassian.com (after checking that you can't enable it in your my.atlassian.com account that owns your Cloud system)
-
That is entirely up to your user base - they can use a resolution to mean whatever they want. But, an "invalid" resolution is generally used to mean "we closed this because the issue does not make sense or is not a valid, useful description of a problem so we can't do anything with it"
-
I don't think you got an answer to this earlier because there are a lot of incorrect suppositions in the question. You do not need a web server to run JIRA. A lot of us put it behind a proxying web-server for various reasons, but you don't need one. It comes bundled with an application server already (you can use a…
-
There's no record of what template was used to create a page, so I'm afraid there is no way to even begin to do this. You could take an educated guess and hope the users have not moved it too far away from the template so you can still identify pages made with one. But that's hard work and may miss pages, as well as…
-
If "you tried with my.inf", then you're either looking in the wrong place to configure it, or your settings are incorrect. To fix this error, you need to configure your database correctly. I'm afraid I can't tell you much more than that, because I don't know how or where you've installed MySQL or how you've tried to…
-
I'm afraid not, because JIRA can't know how to group things for swimlanes if outside the "story + subtask" concept. What would happen if you put in a swimlane like "issue is in subtasktypes()"? Or even "component = X" - it can't group the subtasks under stories if you try to define swimlanes with these.
-
What do you mean by "template"?
-
That's the standard issue view, not the Kanban board. You can change the order by telling JIRA what order you want them to appear in the workflow. Have a look at https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html and look at the opsbar.sequence bit.
-
It already sounds like your hardware is more than adequate to run your JIRA at a decent speed, so I don't think just throwing more resource at it is going to help you a lot. You need to analyse what is slowing it down and why. I always go back to…