Comments
-
No, the resolution date really is "the last time the resolution was set", it's not actually physical data, it's derived from the time the resolution changed. As you suggest, you'll need a custom field.
-
To add a summary of what you'll find there, it's "search for issues, use bulk edit, and move". You won't get "one click", as projects can be configured very differently, and JIRA needs to validate the data and change it to match the target configuration. In a lot of cases, it's going to need to ask you how to change it.
-
You've already got the docs I'd start with. I would not recommend 5.anything to 7. Go to at least 6.3 before the jump to 7 (and I'd strongly recommend 6.4)
-
In other words, follow the documentation?
-
Even if Atlassian did decide to do it (and why bother when there's a free plugin already), it would be distributed as a plugin and probably have almost identical code to the JSU. All the other workflow functions are plugins that they include in the off-the-shelf product, they're no different to 3rd party plugins other…
-
Yes. You'll need some coding though. At the very least, you probably need to tinker with the "seraph" to get it to use your new code. Have a look at http://confluence.atlassian.com/display/DEV/Single+Sign-on+Integration+with+JIRA+and+Confluence to begin with.
-
There are some things you can't do in "draft" mode. Draft mode happens when the workflow is currently in use. The most simple solution is to copy the workflow to a new name, add the transitions in there, and then change the workflow scheme to use the new one instead of the old.
-
Use the issue type in a different project with a different permissions scheme. The create function in a project does not have any way to restrict who can create an issue type - you can either create an issue or you can't. Some people try to play tricks with javascript, but I'd avoid that. There's also an ugly hack where…
-
Ok, the boards should be matched with how you are actually going to work. If you have one big team that does some variation of Agile Scrum (as in estimate, plan, commit to, execute in a fixed time frame and review it), then you should have one scrum board with one backlog as the starting point. If you've got six real teams…
-
I don't quite understand why this board set up might be of any use to anyone, as it will obscure the whole point of having scrum boards. But, my lack of understanding aside. Have you tried using the function openSprints() ? I have a feeling the JQL for your board might be "project in (x, y, z) and sprint in openSprints()".…
-
Oddly, I was having discussions with Atlassian only yesterday about the future of answers, so your question was timed perfectly. I think I'm going to point them at the problems I've expanded on here as well - all good feedback for better answers. Poke me if you have any ideas about improvements and I'll pass them on (or go…
-
Broadly, there are three ways to delete a question. * Admins, of course, can do what they want. However, they rarely delete questions, as the whole point of this site is community help. They tend to intervene in only contentious subjects * Those of us with a proven contribution history can flag people as spammers - not…
-
It's a bit more than just moving from an add-on to an application. Both of them "supplement or enhance functionality" on top of JIRA Core. The main difference as far as the end users are concerned is the licence model. You're probably familiar with the licensing of add-ons for JIRA 6 and below - they have to match numbers.…
-
But there's no actual question here? What is the problem you're having?
-
Have you tried removing all the listed add-ons on the page you've linked to from <a href="https://confluence.atlassian.com/display/JIRA/JIRA+Home+Directory" rel="nofollow noopener noreferrer">$JIRA-Home</a>/plugins/installed-plugins and restarting?
-
Your users do not exist in Jira. Doesn't matter if you say they do, the system does not have them because you've got their user IDs incorrect.
-
This does not quite make sense. If you are creating a new issue, then the field will have no value because you haven't entered one yet, so there's nothing to display in a read-only mode. I suspect what you mean is that "Business Demand" is not actually a field that belongs to the sub-task, it applies only to the parent,…
-
Those are "multi select list" custom fields.
-
You need code for that - there's a few add-ons in the marketplace that can do it. Natively, you can't - JIRA will let you set up a project with the same schemes, but cloning all the issues is simply not in there.
-
Ah, I see.No, you can't. The priority field is a system field that has additional functionality that enables the icon to be added and rendered. The built-in custom field types do not have any icon functionality.You'd need to find/write a custom field that supports the addition of such icons
-
Custom fields don't have icons. Could you explain what you mean by "icon", as I'm not grasping what you're looking at.
-
No, its nonsense because the shape of the data is non compatible Excel holds data as a line-by-line, column-by-column grid. A wiki page is generally a large block of unstructured (but formatted) text. How would you translate that into a table? One (variable width) row per line? Per sentence? Skip a line on paragraphs? One…
-
I have a feeling you can do 6.2 to 6.1, I think that's where I did it. All you do is fire up a new empty 6.1, and choose the "restore from a backup" option. Point it at the xml from a 6.2 OnDemand, and you'll get a big red warning box, but a system built from your 6.3 data will be created on 6.2. I still don't think it's…
-
Not really. Atlassian release "when it's ready" and don't publish much of a schedule. Even partners and experts don't get much warning. Later versions of Jira can import from OnDemand of higher versions though, so you'll be able to take a 6.3 copy and drop it into 6.2
-
Ok, makes sense. The next question is "how are you flagging things as belonging to Pegasus"?I don't actually need an answer to that, it's just that the next thing I wanted to say is that a lot of the reporting in JIRA is based on filters, and what you probably want to do is start with a filter that says "application =…
-
Start by looking at how you are recording this information in JIRA - what is "all work"? What is the "application"?
-
That is the data captured in the issue history. Every line in the issue history contains field/from/to and these lines are grouped by change author and date Some people, for utterly dumb reasons, hack their JIRA to hide or even destroy that data. That's the only reason I can think of that you might not be seeing it
-
Oops, yes, I forgot that bit! Sorry!
-
You have to remove all access to a basic "no one can do stuff" level and then rebuild it. Jira's access control is permissive - you actively choose to let people in, not stop them doing stuff. You've probably inherited the default Jira setup - the group "jira users" can log in, which is fine, but then it's used by default…
-
I'm afraid the due date field is just a date, it doesn't have a time element to it. Best you can do is add a custom field of date/time type and use that instead of the built-in due date. I'm afraid it won't have any of the "due" functionality though.