Comments
-
Short answer - Jira doesn't have a function to do this. That's why you can't find it in notifications - it's simply not there. However, the Tempo plugin does. Have a look through https://tempoplugin.jira.com/wiki/display/TEMPO/Configuring+Tempo+Scheduler
-
Right, that's not going to work.Jira 4.4 only runs on Java 6. But if you downgrade Java, you're probably going to get the same error because you need Java 8 to avoid it.
-
I suspect it's down to a known flaw in java. What version of Java are you running JIRA on? And what version of JIRA?
-
You probably need to give us a bit of context - where are you getting this?
-
For what? If it's for Tarantual, then you'll need Connect add-ons that are written to integrate the two.
-
The sentence "we'd need specific DB info" suggests that your Tarantual integration will need access to JIRA's underlying database. You do not get that on Cloud. Your integration needs to communicate with JIRA via REST or JIRA addons.
-
For Cloud, you can't change it. Atlassian won't do it for you. You have to get another Cloud system set up and then migrate over to it - see https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html
-
It's because the built-in usage stats stuff is frankly archaic and does not perform well. It works, but doesn't scale well. I'm not sure why it's even left in there any more. There's a couple of add-ons I reach for here. View Tracker for Server and Analytics for Cloud - very different, but both seem to get me trustworthy…
-
Ah, you've run into a known flaw in Agile here. Even with the most open permissive workflow in the world, it does not yet support "drag to different status in same column". There is an open issue at https://jira.atlassian.com/browse/GHS-9720 (I think there are similar related ones too, that's just my bookmarked one) You…
-
Not directly, you have to create a new board and replicate all the settings (I usually recommend only replicating the columns and filter at first, as Scrum and Kanban are different and users often find swimlanes and quick filters for one board don't really have that much use in the other type, so a re-evaluation is worth…
-
JIRA 7 application access is a little different - see https://confluence.atlassian.com/adminjiraserver070/licensing-and-application-access-749382677.html
-
This is the same as https://answers.atlassian.com/questions/287075/in-a-particular-jira-project-i-am-trying-to-push-link-the-user-to-a-confluence-wiki-space-page-after-the-user-has-clicked-on-submit-to-create-an-issue
-
Hmm, I see what you mean. It's not able to convert it into the internal format. I'm not sure it's a valid entry without being wrapped in an html type macro, but there's definitely a bug there - it should either store it correctly, or tell you that it can't handle the text.
-
When you enter this, are you using (✓) or something like ? (That's open parentheses, slash, close parentheses) What does the log file say when you do it?
-
Probably because it's been revised as the landscape is changing...
-
* Throwing more resources at it * Better housekeeping * Expert tuning (both app server and Jira level knowledge - Jamie Echlin's tip about using "everyone" for "browse" instead of "jira-users" for example) * Simplification (which reduces the usefulness of the system) * Deleting issues, which causes a need for archiving,…
-
Yes, but again, it's a spot of coding. I wouldn't recommend removing the quick-search, it can be very helpful for your users, but it's your system and you can do it if you want. I seem to remember it's in a .jsp file, so you can simply comment out the segment that provides the search text and box, and add your other logo…
-
You'll need to edit the code to change the footer (and if you do, remember not to remove the "powered by Atlassian Jira" bits, or you'll breach your license). For the header, I'm not sure quite what you want to do - you already said you can change the logo in look & feel, so could you clarify what that cannot do?
-
Right, that's the easy one ruled out (95% of the times we see this, it's a simple routing problem). The next step is to run through https://confluence.atlassian.com/jirakb/how-to-fix-gadget-titles-showing-as-__msg_gadget-813697086.html Although you have already dealt with the routing, and your description probably rules…
-
Ok, that sounds like it's right, but we should check the whole route. On the JIRA server, try "wget http://[DNSName]:8080" - does that grab your JIRA dashboard/login page?
-
That almost always means that the JIRA server is not able to reach itself using that url. Can the server resolve that name back to itself? What does nslookup <your host name> give you?
-
Have a read of the docs. For this particular question, start with https://confluence.atlassian.com/display/JIRA/Associating+Issue+Types+with+Projects and https://confluence.atlassian.com/display/JIRA/Configuring+Workflow
-
Creating buttons requires coding, and that code needs to point to the actual sub-task creation. You need to fix the "cannot create" first because your code will need to use it.
-
Does the actions menu contain "create sub task"?
-
Have you included at least one subtask type in the project issue type scheme?
-
What is the problem/question?
-
You can't really do this - you are looking for an absence of data rather than data that exists. "None" means "there is no data here". Not a "null" or "an affirmitive data value meaning none", it really is nothing. Let's say you have four issues, one at each level of severity. If you go and look at the database, you will…
-
Yes, but you need a bit of coding to do it - a listener to pick up the "issue reassigned" and "edit" events, read the subtasks and re-assign them all automatically.
-
That makes sense. It sounds like the setup is one Jira install, and you have two accounts. Your first client has given the right groups and roles to the account they gave you. Your second client has NOT given you the right groups and roles on the second account. It's not very clever of them to tell you to come here for…
-
I really don't know. I don't know what your setup is. You haven't said whether it's two separate Jira instances or one, you haven't said what your access model is, or how you expect to get into the second client's systems