Comments
-
Ok, then you'll need to pay someone else to write a converter.
-
Change your full name for your Atlassian account to be your user name.
-
I'm not sure I'd do this with a board, seems like overkill. A simple filter for "resolved > startofday() and resolved < endofday()" shown in a dashboard gadget would list all resolved (delivered) items.
-
Assign them all to the admins and keep re-opening them until they fix the problem ;-) I know, very passive-aggressive, but your admins are failing you and need to do better.
-
I'm not sure what you mean by "template". Your call to create an issue looks ok to me, so I'm not sure what's going wrong. The xml you've given is of no use for REST calls, so I'm guessing I am missing some part of a process you are going through that you've not explained. As an aside, projectTemplateKey is not a parameter…
-
Please read through the release notes for each minor release (7.3, 7.4,7.5, etc) You can find them at https://confluence.atlassian.com/jiracore/jira-core-release-notes-781386726.html
-
Ok, good. There's several ways to do this, but it's better to look at what needs doing before talking methods. The change you need to make is relatively simple. There is a table in the database called cwd_user. This holds (amongst other stuff), the login id, the data that connects a user to a thing in Jira, and an email…
-
Ok, that keeps it more simple. I assume your Okta is the usual usage - it's effectively a password safe, rather than an authenticator?
-
It depends on what type of user directory you are using and your username format. Is it the internal Confluence directory? Is the user name format a simple "login" and not their email (e.g. when logging in, I'd enter "nic" in the username box, not "nic@mydomain.com")
-
Comments is not really a field, it's a collection of entries in a database handled differently to most fields. You don't need to add it to screens, the system handles it automatically, giving a comment box whenever a user needs it.
-
It's horrid when you are forced to work around things your admins should have fixed! The tool is supposed to be there to help you, not get right in the way. (I'm mostly blaming the admins - there's aalways a chance of a Jira bug of course, but the symptoms you've got scream "broken transition, caused by bad config or a…
-
I made a resolution about 9 years ago - to not make any more resolutions. I'm still going strong. I do set myself birthday goals though - by birthday time next year I will have learned/read/done/been-to something. I find resolutions a bit too fuzzy and prefer measurable goals.
-
You would need to hack code in Confluence to get it to look up the data and display it. I would be more tempted to do this in Jira - use ScriptRunner to create a "scripted field" that looks at the links and their status and displays that, then use that in the Confluence report.
-
Yes, you have to pre-load the project with the tags you intend to use. You could use CSV imports to pre-populate it. I went a different route when I did it. We had a load of existing tags with unique IDs that were not Jira keys, so we continued to use that field. It was, of course, a field on the Jira issue, and the code I…
-
Oh I agree, definitely. I was just saying that when you do have knowledge, you can see how Jira ended up doing it this way. But it's badly worded and presented to the users, forcing them to either learn the structure, or learn a clunky routine.
-
Creating boards and sprints is part of the configuration. Cloud doesn't have a method for transferring these.
-
SQL is the single worst possible way to report on Jira, please do it properly with the UI or API. If you insist on doing it the wrong way, look in the changeitem table, which you'll then need to join to at least two other tables just to get the basics out.
-
You already have an account that uses that email address. Stop trying to create a new one, and use the existing one. If you have forgotten the password, try the "forgot password" link on the login screen.
-
It does sort of make sense when you get the underlying structure, but if you were to say "it is worded really badly in the UI and counter-intuitive everywhere it is explained", I'd completely agree.
-
No, you need to go to the server file system to read the logs. The support.zip file does contain chunks of them, but I tend to find the plain logs with everything logged can be more useful. Although I've spent the last <mumble> years with Jira, so I'm quite at home with getting everything and being able to skim them. Have…
-
I can see why a few jobs aren't a problem. What worries me is how you're getting them running, as none of the other Jira systems I've got are running anything. They do add lines to the table. But they don't do anything. I suspect something else is going on. Just because there's a line in a database table doesn't mean there…
-
This is well worth checking. It's something that bites me a lot when I'm doing SSL stuff, but I forget it might cause issues in other areas!
-
Mostly the cached value. It sees the Lucene index as the "source of truth", but in most cases looks for the cached value before reading the index. (This is a lot of the reason I say "oversimplified" when I say "scripted fields are calculated when indexing")
-
Either "Bug" is not a valid type for this project, or the configuration is different to the others you do see on the list. Check all the schemes for differences (although I suspect it's going to be workflow or field configuration)
-
Have a look at https://confluence.atlassian.com/jirasoftwarecloud/configuring-a-board-764477974.html and focus on the filtering parts.
-
What does the log say when you try that JQL in the search?
-
If it helps, there's an oversimplified way to think of it. The fields are read-only because they are calculated, not entered. A scripted field's data is updated when the issue the field belongs to is re-indexed for any reason. You can't modify the values of a scripted field because they don't really exist.
-
Since we're both stuck, I'm going to poke Atlassian and see what happens. I can't understand why your load goes up apparently in correlation with these jobs when other Jira systems add the jobs but do not.
-
Oh very much so. I do wish they'd put exactly that phrase into the sign-up page for English/European-language speakers because we all know what to expect when we're called that! Random vaguely related trivia - the very first Nobel prize for medicine was awarded around 1900 for a diphtheria treatment, developed by testing…
-
I could be a bit grumpy and respond with "since you are not reading the answers", but I do understand that my writing has been quite terse today, so that would be just as unfair. Instead, I'll try to rephrase: >How would I go about adding another panel instead of description? You need to create and install a new add-on…