Comments
-
Look at the workflow diagram - you should see that every status has an incoming transition from "all" (in a little black box) That means a user can always move an issue from any status (including done/closed/ended/whatever) to any other.
-
You can't do 1, that's why the issue I pointed at exists. What you do is create workflows which have limited resolutions (see the issue I pointed at for details towards the more recent comments) and then associate them with issue types.
-
You can't. You can get close, but it's by *workflow* rather than project. It's also vastly ugly and a mess to maintain, and should be fixed properly. Lots more information on both of those statements at https://jira.atlassian.com/browse/JRA-3821
-
You can sort of split this requirement into two parts. You need hosting (other than OnDemand) and you need administration as well. A lot of Atlassian hosting providers will give you the flexibility to add plugins, but the administration stuff is another option. You'll need to vet the various providers to see what level…
-
Iterate through every page within the space, and ask your DBAs how much the rows comprising the content and history take up, then add the size of all the attachmnets.
-
Go to "issues", search, then save it.
-
Add a condition to the workflow for "sprint is not empty". I'm not sure you can do it in plain JIRA, but if you add the JIRA Suite Utilities add-on, you should find it can check for the field.
-
1. Yes. An export is "everything", but you can import "everything" or single projects. 2. It will keep the numbers 3. Yes, if you want a proper history 4. Yes, it's in the docs, I don't have it to hand. If you go over it, you will be charged more though, so it's not a hard limit. There is a problem though - project import…
-
You need to log in as an admin, go to the list of resolutions and check the options. If there is one on the list there called "unresolved", you have a broken system and you need to fix it. Rename it to "broken resolution, do not use me" or something equally clear.
-
Check the groups for your user and your other administrators very carefully. I suspect you're missing from at least one group that they are in - make the accounts identical. If that doesn't fix it, you'll need to raise the problem with Atlassian.
-
If you can't find the macro in the macro browser, then it's quite likely that the add-on has not been enabled properly. Can you check that the add-on looks ok in "manage add-ons"? Fully enabled and showing modules with the macro names?
-
No, you need to login as a Software user to see a Kanban board.
-
You can't in the UI. It's actually quite easy in the database though (caveats - NEVER run SQL on a Jira while it is running, and ALWAYS backup before you do this, and do a full reindex afterwards) See https://confluence.atlassian.com/display/JIRA/Changing+Custom+Field+Types Note that you can't go the other way, unless…
-
For JIRA 6 and below, you need JIRA + Agile add-on + Service Desk add-on. You download JIRA and install the add-ons from the UPM. For 7+, you need JIRA Core + Software application + Service Desk application. You can download JIRA Core and add them both. Or you can download JIRA Software and add Service Desk. Or you can…
-
What are you doing to get this error?
-
The Cloud migration doesn't really matter, but have a look through https://confluence.atlassian.com/doc/database-setup-for-sql-server-9258.html https://confluence.atlassian.com/confkb/known-issues-for-sql-server-119669.html The thing people seem to trip over most often is the collation, so check that carefully
-
Again, have you raised it at http://jira.atlassian.com? If you don't raise it, no-one is going to do anything about it, and you can't expect other community members to raise it for you. That Jira is where Atlassian track requests and that's where it needs to go
-
Have you raised it at http://jira.atlassian.com? (or found an existing issue to cover it?)
-
Every board is based on a filter. It's often something like "project = X", although you can make far more complex ones. Such as "project = X and issuetype != Epic", which I've seen many times. Check the board's general configuration for that. Post the filter here if you're uncertain, and check that the Epic matches it by…
-
Make sure that one or more boards have filters that include it.
-
Add-ons are independent of the operating system, they run inside Atlassian applications
-
Generally, none - don't mess with the database behind Atlassian applications. However, if you insist, then you'll need to be a bit more clear on what you mean by "content notifications". The record of what Confluence thinks it has sent? The config that tells it who to notify? etc?
-
Um, it looks like your code is setting param1 to a set of files, but then posting the whole set in one go. Could you try posting a single file?
-
You don't seem to be iterating through the attachments, just throwing them all at it in one go. Can you try one at a time?
-
Look for "attachments" and POST in the API doc. You'll need to call the post once for each attachment https://docs.atlassian.com/jira/REST/latest/
-
The difference between variable types still catches me when I'm scripting. Although I completely understand why there are types, coming from a school of coding where every operation mattered, you explicitly tell the code to use the most efficient (working with integers is faster than longs, which are faster than doubles,…
-
Where is this script running? If it's a post-function, I'm not sure you need import anything.
-
You're close, but there's a couple of things to understand about the estimate field. First, it's a length of time, and held internally in either seconds or milliseconds (I can never remember which). So you need to feed it a simple, large number Second, the 10d thing is done in code for the front end and it's about making a…
-
* Go to Admin -> Time Tracking, and turn off "pretty" time formatting * This is already "right". It's going to stay as seconds because that is the best option JIRA stores and exports the duration type data in seconds because a few people might need that granularity. Most need hours or minutes to be frank, but storing it in…
-
No, there's no way around it. Jira doesn't have locking or conflict resolution. You'll find the first commit is overwritten by the second, unless the first commit makes a change that changes the security such that the person doing the second commit no longer has the right to do it.