Comments
-
You don't. You can copy and paste it in as a table, but you can't embed anything more clever than that.
-
You do not get it. System admin is for Cloud support only. You should have application administration as the account holder, and you'll be able to delegate that to others.
-
How do you know they are waiting for your action? The standard approach, and the best is that if an issue requires action, it should be assigned to the person who needs to take that action. So you'd simply look for "assignee = current user and resolution is unresolved" to find everything you need to do. It sounds like you…
-
Plus, I can't find a way to swap it back in the UI config. I may have to resort to hacking... urk.
-
Yup, sorry. Too close to upgrades and coding. We all make mistakes sometimes ;-)
-
Actually, I'm terribly sorry, I've misled you completely. My fault, I'm in the middle of upgrading a plugin that displays subtasks and I was looking at that and not the actual filter results gadget. The picture you've posted IS the old 4.x display. Version 5.1 (And I'd assume 5.0) has been changed, so that summary says…
-
You shouldn't have to do anything special to get that display - simply showing the "summary" field should do it (does here - Jira 4.0 and 5.1)
-
Indeed it will go away when your Cloud licence expires. You can export it all to xml though, but it won't be of any use to anything other than another pair of JIRA and Confluence systems to import. Unless you massively re-engineer it all into another system.
-
You'll need to think about how you're going to present this data to the operational staff. The current format? A big block of documentation built from the current data? Does it need to go in another system? As one idea, is there something wrong with simply making it all read-only when the project ends, and just leaving it…
-
Have you tried Admin -> Look and feel ?
-
There doesn't seem to be qn equivalent page for JIRA 7 yet, but https://confluence.atlassian.com/jira064/jira-requirements-720411866.html still covers the sizing. https://confluence.atlassian.com/adminjiraserver070/supported-platforms-749382629.html has versions of compatible stuff for JIRA 7+
-
You might want to check the internet for what iCal is, there are search engines. I don't think there's any point in talking about iCal and Confluence events until you know what they are.
-
I'm sorry, I was not clear there. The task type does not matter, what I was asking about was the type of link, or, in more abstract terms, the "relationship". You could use "issue links" to link an issue to another. You could create "subtasks" on an issue, which implies a parent-child relationship. And the one I'm…
-
Are you sure these issues are links or subtasks? And not Epic Links?
-
All I can suggest is that you try it. I don't know all the possible marketplace entries.
-
Then you can't do it. There's nothing in JIRA to draw a burndown chart (remember, Core is an issue tracker, not an Agile tool). So you need to add the function. Which means add-ons. I'd recommend the Agile one for your version of JIRA.
-
You can share the edit screen with the transition though (one screen, same fields, used in the transition and for edit actions)
-
Go to the space permissions and allow "anonymous" to access it. That makes it public without using any of your licences.
-
Yes, an array of options IS an object. Your variable "example" will look like a generic object, but if you delve into it, you'll find it's an array.
-
issue.getCustomFieldValue(customfield) will return an array of the currently selected options, which you can then iterate over to get the list of options. (Sorry, I don't use python, but that's the java api call which will do the job)
-
Do you mean the options currently selected on a custom field for a particular issue, or the whole list of possible options for the field for a given project and issuetype?
-
Look at the issue history, it contains a full history (The activity can lose older events)
-
I think it was answered with "you can't", natively. JQL searches for issues flatly, it doesn't do "read a list and do something with the contents of that list" type things. Your thought about what is missing from your query is spot-on - "or issuetype = subtask" really does mean "all subtasks", and you need to filter that…
-
Do you not have a series of numbers (of pages) and a "next" arrow on the user list screen? I do (Beneath the drop-down for "users per page"). What do you get if you reduce the number of users per page?
-
Lotus Notes is an attempt at a computer system to do everything. Most of the industry regards it as a bit of a joke because it's compatible with nothing, and despised by the people who have to use it due to terrible UI, unreliability and massively pointless complexity. I'm hoping you're here with the intentions of…
-
Ok, that's a useful thing to know. Without seeing the logs, it sounds like it's starting and running ok, but that it's not running where you expect it to. I've done this a few times myself - reconfigured Tomcat to present Jira somewhere else and completely forgotten to restart it to pick up the changes. It's quite likely…
-
Hmm. From that, I'd say your virtual machine is not configured to automatically restart Jira when it's rebooted. You can check that by comparing the Jira log with the reboot time, although it may be that the Jira log has no entries for a while before reboot, if Jira was not being used at the time. Check the OS settings for…
-
Oooh, no, they don't. They really don't. When you re-rank an issue, you're effectively re-ranking every issue in the system. That's the technical and logical effect, but of course we can cut it down and assume you only mean issues around the one being moved. That would mean a simple "move issue several lines up" is cut…
-
That's what we're getting at - you use the Jira project. Because jira.atlassian.com is a Jira system. https://jira.atlassian.com/browse/JRA If Atlassian decide your issue is with something else, they'll move it. Let them worry about the difference between their services and technologies!
-
Then, as Taiwo and Udo have already said, log them in Jira at http://jira.atlassian.com Let me try to explain this again: * jira.atlassian.com is the "service" you want to report problems with, or ask questions about.* This service has an issue tracker for questions and problems * This issue tracker is the Jira found at…