Comments
-
Yes. (That's a nice short answer. I'd add that there's a few changes which means you might have to fiddle with the setup of your projects as the way defaults apply have changed, but you can still do everything you describe together)
-
What are the errors you are getting?
-
See https://confluence.atlassian.com/jira/customizing-email-content-185729653.html
-
Jira permissions are a simple "permissive" scheme - that is, they start on the assumption that you cannot do anything, but then you add permissions to do things. There's no "block access to" function, you have to remove the setting that was allowing the user to do something. For your group, start with the assumption that…
-
There is no solution in Confluence, as you've read below. You need to establish WHY this is occurring and look at two things 1. Why is it a problem for you 2. Why is it being done like that
-
You still shouldn't have two users with the same login and password. As I said, it's illegal in certain cases, and probably breaches your license. I do think I know what you mean - imagine the case where I log into Jira on my laptop. Then pick up my tablet and do the same - you want the second login to fail because I'm…
-
There's not really enough information here to tell what you're doing or what the problem is. It does sound to me like you have given a single username to many people, which is a really bad thing to do (technically, illegal in certain places, and probably breaches your license). But I can't tell.
-
If JIRA doesn't appear to start, you need to read the log file to find out what the problem is.
-
What does the log file say is going wrong?
-
A field in JIRA is either required or optional when you do it in the field configuration. You either need to put it on the screen so that it can be filled in (because it's required), or make it optional and do the "mandatory" thing later. Usually, people use validators in the workflow. A common example might be a "root…
-
The error you are getting is Jira saying "either your machine or I sent a packet to somewhere else, and I got no response within a reasonable time". This is almost always a network error, although you can cause it with bad coding, or doing unusual things on the client. The fact that it's happening for you and not every…
-
Ah, that's Jira telling you that your network has closed a connection it was trying to use. Happens on slow, overloaded or badly configured networks sometimes (I've provoked it at home when I allocated two machines the same IP address for example). I'm not a network expert so I can't really tell you a lot more than it's…
-
You have to formally end it (you don't need everything in "done" to do that, although it is the aim of the sprint!). See https://confluence.atlassian.com/agile/jira-agile-user-s-guide/working-with-sprints/ending-a-sprint
-
No problem, could be the same thing though!
-
It is possible to listen on just ipv4 or 6 (although generally most systems listen on both if they're enabled), it's worth explicitly testing both thoughThe log is atlassian-confluence.log - that's the main application log. A blank screen implies Tomcat is running and listening, but not a lot else, and the main app log…
-
What does the Confluence log say when you get the blank page on port 8090? Also, you've given an ipv4 address, then said netstat is listening on ipv6 port 8090 - have you checked it's listening on ipv4, or what you get it use the ipv6 address?
-
You should always use the latest server version available.
-
You should always use the latest server version available. It might work with 7.1.8, but it is strongly recommended that you use 7.2
-
Are the issues to be released all in the far right hand column of your Kanban board?
-
I have to agree with Harry. The workflows in Jira are representations of PROCESS. As such, you want your issues to represent things to be worked on, they move through a process/workflow, changing status as they do. Your status should be things like "defining requirements", "in design", "under development". Your issue types…
-
Add a new field of type "free text" and delete the old short-text field.
-
Sounds like you've created a "short text" field. You can't extend those. You need to swap to using "free text" fields instead, they're unlimited.
-
I'm not sure what you mean by "characters in a renderer"? Do you mean the characters in the long-text fields? Which are effectively unliimited?
-
Atlassian release "when it is ready" and do not give fixed release dates. You can see when something is nearly ready by generally watching Answers, mailing lists and documentation changes, and a really good indicator is the version that OnDemand is running - that's on 6.2 which implies a release for the rest of us is close.
-
Bamboo is a build and release server for doing continuous integration and deployment Crucible is a code review tool So, no, as they're too totally different things.
-
No, the created date is always the date you physically created the issue. The exception is if you import issues with CSV, you can set it in that data. But you can't change it. If you're logging issues and need to record a different date/time to when you're typing, most people use a custom field to record the actual date.
-
Please see the answer to your previous question at For post function confiuration
-
That doesn't tell me anything about the field, or what the problem is, it's a permission.
-
Ok, the padlock is not a native JIRA function generally. If you can't edit a field, JIRA will tend to hide it or grey it out, not put padlocks next to it. What type of field is it?
-
I suspect you have the "Field security" add-on and it's been configured to block your access to the field. You'll need to get the config changed.