Comments
-
Ah, an old favourite. Usually means JIRA is too loaded to start in time. Start debugging this at https://confluence.atlassian.com/display/JIRAKB/Troubleshooting+JIRA+Startup+Failed+Error
-
Yes, you can do that. The system priority field is global, but you can hide it using field configurations - that goes down to an issue-type level, although I'd recommend not doing that and sticking to hiding/showing it at a project level. Briefly, you'll need to set up a new field configuration (I'd copy the existing one…
-
What are you expecting, and what is actually happening? Have you re-indexed?
-
What "font file", and do you mean JIRA or Confluence?
-
No, it doesn't track administrator activity in making configuration changes. It sort of assume trust in administrators, and that there's no need to track them. In the places I've worked, I've always been able to trace admin changes back to a Jira support issue (rule: do nothing as a Jira admin unless you've got a Jira…
-
1) I don't think created date is appropriate for this - it's actually the date a user enters the issue into JIRA, so in the future, it's not going to make a lot of sense. JIRA doesn't really have a duration either. The estimate fields are for estimating how long something will take, in actual time, not duration, and then…
-
That looks fine, so back to the four questions I asked before - could you explain those?
-
Ok, but how are you mapping the fields on import?
-
Ok, 1) What are you using for start and end date in JIRA 2) How have you set up JIRA to do the calculations? 3) What are you using for %complete? (Did you import some form of estimate and worklog data?) 4) I don't know what you mean by predecessor and successor here?
-
Don't know. I'd ask the admins who set it up in your system (rework is not a standard issue type, you've added it)
-
"View workflow" is controlled by the project permission scheme, so check that first. "Bulk edit" is a global permission - check the "global permissions" to see which groups are granted bulk facilities and make sure you are in at least one of the groups
-
No, there is no "issue cloned" event. The internal systems don't really see a "clone", they see "new issue", even though all the data is scraped from an existing issue. I suspect you need to trap a "create" event instead, then scan it to see where it was cloned from - you can look for the "clone" added to the summary, or…
-
It's not an installer, it's just the package that makes up the add-on. Go to the "versions" option in the add-on page you've linked to, and to the right, expand the "all versions" bit. Click the version you want, and it'll download the package, which you can then upload on to your Dev server through the ui.
-
You should issue a REST call to Jira in your c# program. Tarun has given the links to the examples of what your c# code needs to do.
-
An issue belongs to a project. It's nonsense to have an issue appear in another project when you've created it in a specific project (and possibly hard work because the projects could easily be configured differently). If you mean you want a copy of the issue, then Udo's answers are correct.
-
It's not location, it's purpose.Assignee is a field. Search parameters are not the same thing, they're questions to ask the user. And they have to be different anyway - the assignee field is limited to "who can be assigned an issue in this project" and the search has to be able to select anyone.However, autocomplete works…
-
The usual culprit is that you don't have the global permission for "browse users". This affects all the user fields though, so an easy test is to see if the reporter or other user-picker field has the same issue.
-
Columns are not based on resolution, they are based on status. I assume you have Done, No Longer Required and Rejected as status (possibly as well as resolution, which is a little redundent) Most simple option - put all three of those Status into the done column. When a user drags a card into the column, they'll be given…
-
The question was about renaming the space. Not changing the key.
-
It's roughly where you'd expect it to be: Space Tools -> Overview -> Edit Space Details
-
So by "load", you mean "create sub-tasks" and "template" means you want to fill in some fields. I'd use one of the "create sub-task" post-functions. You may need to look in the marketplace for suitable ones.
-
No, I am sorry, but it is not clear at all. An issue in JIRA has a status. A single status. It can have only one. "assign to each status" says you want issues in all status, which is nonsense.
-
Start at https://developer.atlassian.com/jiradev/jira-platform/guides/projects/tutorial-creating-a-project-template Some of your question is not clear to me though, on a couple of points. * You will need to create issues first, so that your sub-tasks have a parent to live under. * Sub-tasks are issues, which move through…
-
You'll need to write some code. Creating and sharing a dashboard do not fire events, so there's some stuff you'll need to hack into the core of JIRA, then something to catch it and email people.
-
No. Only one application can use a port on a server at a time. It's not an Atlassian restriction, it's everything. That is the reason you end up with mod-proxy type tricks - that's one single application listening on the port and redirecting traffic to a set of other applications, making it look like they're all on one…
-
Having said that, you might be able to do something with a Connect add-on to at least calculate and display sums etc. And I am certain that there are people out there trying to write Connect add-ons to give us this sort of flexibility, so this may change. Hopefully soon.
-
It's not, there's no real scripting available on Cloud
-
Yes, but the JIRA downloads come with an internal file/memory based database. It's no good for production (it will fail, catastrophically, at some point after a while of use), but good enough to run an import to test. Ideally, you should use the same database as the system you're trying to test, but a test that you can…
-
You have answered your own question - "create a test instance and import the backup file" The import will overwrite all the data in the test instance, but that's the whole point of a backup, it's supposed to recreate the system you backed up. You can download and install a standalone JIRA instance with which to test this…
-
There's nothing specific in Jira to do this, but I would look for a "listener" that catches "work logged" events, has a look at the issue the work is logged on and then pings you an email or some other action. (I've used the script runner to ping a message into IRC in similar cases, but it was in Jira 4...) The quick…