Comments
-
No. You're either an admin or you are not. Project users can see the config of their projects though. Everything else, you'll need your admins to extract and document.
-
See JIRA Misc Custom Fields - how tu sum Values and put total in numeric column
-
As well as going back to a smaller overall memory space and then building up slowly as Zulfadli says, you need to tune the rest of the settings in line with each increase. It really is not as simple as just throwing more memory at it, there are consequences. You need to read up on Java memory tuning.
-
Because you're not giving it enough room in your memory settings. Try changing them as per the doc I linked to.
-
Simply throwing more memory at a JVM is not a good answer. You need to look at what the problem actually is. Start with https://confluence.atlassian.com/display/JIRA/Increasing+JIRA+Memory
-
You'll need to explain what pgpool-ii is.
-
Go to "manage applications" and add it from there on Server. For Cloud, log into your "my atlassian" account and add it there.
-
If you can't see the project, you do not match the rule for "can browse project" in the permission scheme. You need to get that checked with your JIRA administrators. It sounds like they could be making incorrect assumptions - get them to show you the project permission scheme, which should tell you why you don't match.
-
There's an additional flag for Assignee. Log in as an admin and go to Admin -> General settings Look for the "allow unassigned issues" option and enable it. You will now find assignee offers you "unassigned" as an option (and usually the default).
-
Nope. It's Epics -> Story -> Subtask. Tasks are the same level as stories.
-
The manual covers it. See http://confluence.atlassian.com/display/JIRA042/Customising+Email+Content
-
I can't help you with the add-on, I've only ever used it for read, but a word of warning on editing JIRA databases - don't. You have to understand them completely if you want a working JIRA afterwards, you must never change it while JIRA is running, and in most cases, you will need to do a re-index after restarting.
-
>a work item in JIRA (not the work itself) is done when the status is changed to any status within the "done" set of statuses Ok, so those status all go in the "done" column. >As I explained in my second example we replicate deferred worked as new tasks in subsequent sprints That is not how sprints work. >what tasks will…
-
But when is an issue done? (Cancelling them is fine, it's a done status, as you're not going to be working on it any more). The context is not relevant to the question, because it's either "more work needed" or "no more work"
-
I understand that desire, but could you explain when an issue is "done"? It's a pretty black and white thing - either it's finished, or it needs more work.
-
I'd +1 that if I could - more than one "done" column is not an Agile pattern. Either it's done or it's not.
-
No, the far right column is "done", the others are not. You can put many status into "done" though.
-
Yes, near the bottom of https://confluence.atlassian.com/display/AGILE/Using+JIRA+Agile+Simplified+Workflow there's a statement "Your workflow only uses Post Functions, Validators, and Conditions which are provided by Atlassian (not any which are provided by add-ons);" - that covers the JSU conditions and post-functions -…
-
Correct. Although you can have multiple status in a column under simplified workflow, it doesn't really add a lot - most users stick to the 1:1 relationship. It's more that your project admins can still change things and if they do, you could easily lose all your conditions and post functions,Also, the last time I looked,…
-
There's a couple of points here. First, the simple one. If you are using the JIRA Agile simplified workflow, then your specification is wrong. The simplified workflow maps status to columns on a 1:1 basis, and allows your project administrators to change the workflow (it's indirect - they do it by changing the columns on…
-
It's at https://www.atlassian.com/software/jira/pricing?tab=cloud That gives you the service and the support for it.
-
>When I start Bitbucket server 4.7.1, the browser is blank. When I stop Bitbucket server 4.7.1, it show errors on the browser "The service temporarily problem" That is exactly what you get when your service is running, but you're looking at a url that isn't defined in the application. And the dead service message when it's…
-
No, it means there is something running there, but not serving up any data. With the logs you've shown us, it really does look like the application is running fine. So the only real option is you're using the wrong url for it.
-
The logs you've posted are showing it running. If a browser gives you a blank screen, then there is something running there, and the logs will tell you why there's a blank screen (Assuming you're hitting the correct url). If it was not running something, a browser would give you a page not found error.
-
Your screenshot of the blank page doesn't work for me, it just shows a menu bar from some application that isn't a browser. Could you tell us what you get in a browser? The reason I ask is that the shortened versions of the log you've taken pictures of indicate it's working fine, which means the problem is down to how…
-
>I cannot access to Bitbucket server even the log states that Bitbucket is running. Ok, what does "cannot access" mean - what's the error or symptom? Are there errors in the log?
-
What does "port dropped" mean? Is Bitbucket still running? What does the log file say when it stops or "drops" (whatever that means)
-
If they don't give you an existing admin account, then yes, you'll need to add one, and the doc does suggest a login id of localadmin But re-read the password bit.
-
Not "retain", no, you have to have a user in the source system that is a known administrator. However, it's quite easy to get one in if you're going to need to. The easiest route is to get the source admins to tell you who has admin, and set their password to something you know, either in the XML or after loading it into…
-
It's a good place to get help from the community, but Atlassian don't automatically raise bugs for their developers from questions. To report a bug, visit https://jira.atlassian.com/browse/CONF - but before you raise it: * Decide if it's really a support request - if it is, then you need to…