Comments
-
I assume the field has been made "required" in the field configuration scheme? If so, then my best guess is that you have not associated that field configuration scheme with the issue type in the project you're using.
-
Ok, three options 1) Use a scripting add-on to provide a scripted field that pulls the data out of the history explicitly 2) Find or write an add-on that does much the same 3) Create a user-picker field, place it only on the "view" screens, and then use a post-function (again, probably from an add-on) that populates it…
-
Script Runner, Jira Misc Workflow Extensions and Jira Workflow Toolbox all do it, and there are probably others. I usually try not to make specific recommendations because questions like this don't tell me enough to select a particular one that would work best for you. You might have other needs that some add-ons might…
-
No, you need to get a list, sort it, and select the first row.
-
I'd want to read the JIRA logs for more detail on what it's doing. You may want to turn the logging detail up as well.
-
That's only if you've added the add-on that provides an additional custom watcher field.
-
All you can really do is filter for "project = x" and sort it by "updated", then read off the first line.
-
Thanks, that's very clear now. a) You have a post-function on the transition that takes the issue into "done". This is setting the resolution to "done" and overriding what the user selected. Remove it b) Opposite answer to a - you need to add a post-function to any transtions from "done" to any in-progress or to-do status.…
-
The log file is likely to tell you more about the error. "Connect timed out" usually means that JIRA can't reach the mail server for networking reasons or the mail server not running on that server/port/etc. It still might be incorrect credentials though, depending on how the mail server responds to that error.
-
In the tables named fieldscreenscheme* in the database. Why do you ask though? The database is not something you want to use for reporting, and you definitely don't want to write to it.
-
No, you'll need one of the add-ons that provide post-functions to do it.
-
JIRA Core is now an application. If you're using JIRA, then you're using JIRA Core. JIRA Software runs on top of JIRA Core. Same framework, uses a lot of the Core, but the easiest way to think of it is that it "adds lots of functions to JIRA Core" You *can* have separate users. If you licence 25 people for Core, then…
-
Eh? Confluence is a wiki-like application. Not a migration add-on. Try marketplace.atlassian.com
-
Ok, we typed the last few comments at the same time. You're trying to merge one system into another. This is an absolute nightmare to do in SQL. The "import" of one issue could affect between 5 and 60 tables, some needing multiple entries. Then you'd need to deal with the possibility of clashes. And the structural data…
-
It's very clear, except on point 4. A board contains a set of issues you select with a query, so if you want ABC-123 to appear on the 1800+ issues board, just add "or key = abc-123" to the query. I think the crux of my failure to grasp it is the word "link". What do you expect this "link" to do? What would the user see,…
-
Ah, ok. Well, that's never going to be simple to represent, or work out, but it's a perfectly sensible requirement. JIRA doesn't really support that directly, it's heavily focussed on issues over people. So it's better at saying "you spent this much time on issue X" than "person Y did Z". What you need to look at is, I'm…
-
Ok, that's good, but leads to the next question - import what? Are you trying to 1. migrate a JIRA system running on H2 onto a PostGreSQL backed one (e.g. turning a trial, test or demo system into a proper production one) or 2. import bits of one system into another (a merge)? (I should warn you though, either way, you…
-
You're looking for "A filter with a second input that refines it further". JIRA does not do those, it expects a user to build the filters they need. I understand the desire to do this, but I've found it often leads to people really not understanding the results. An admin has "spoon fed" them part of their filter, so they…
-
It's working for me. Here's the two 2.2.9 download links direct in case it's something flaky on the page. https://www.atlassian.com/software/confluence/downloads/binary/confluence-2.2.9-std.zip https://www.atlassian.com/software/confluence/downloads/binary/confluence-2.2.9.zip
-
There's no context here to help us understand what you are doing. Why are you looking at the database? What type of "import" is this and how are you doing it? What are you actually trying to achieve (in terms like "build a test machine from production", not "I want to import")
-
I'm still not sure what you're looking for. Let me try a different tack.I don't understand the original question because it was not comparing systems that do even similar things. It was like asking to compare a word processor with an operating system. Different things.The new question is slightly better, but has no…
-
Depends on what you're doing and what you want from it. If you're doing Scrum, then you will want the estimates on the stories, as that's where JIRA Software will work with them. If you're not doing Scrum, and just using plain JIRA or JSD, then estimating the sub-tasks will work for you. The issues can display all the time…
-
That is what the docs say to do.
-
I'm afraid that doesn't really help. The total time spent in a sprint is simple - search for issues in the sprint and add the "timetracking" field to the navigator to see how much has been logged.
-
No, an import of everything will effectively duplicate the old system. But you can selectively import projects and spaces without inheriting all the other stuff.
-
Not a dictionary as such, but probably better because it'll cover all that and what you can do with JIRA - start at https://confluence.atlassian.com/jiracorecloud/getting-started-with-jira-core-765593070.html
-
Yes, it's an interesting digression, but you're right, I think it's a different topic ;-) The klduge option will work, where you store version data against an issue, but it's going to make your data grow alarmingly fast, for no benefit to the users. I'd still go with "proper logging of upgrades" and then some custom…
-
Yes, that all looks right.
-
I'm sorry, that does not make sense. A filter is a pattern which finds a list of issues according to the rules of that pattern. An issue is an issue, an entity with some data on it, representing something that needs (or needed) attention. There's no "link" between a filter and an issue, they're two separate and different…
-
That's captured in the issue history already. Can you not use that?