Comments
-
Yes, you can export a workflow, change the IDs of transitions and re-import it. Not sure that there is any useful benefit in doing it, but it can be done.
-
The setting you've changed changes the rules for how it decides who the automatic assign goes to. You can't actually change the default value of the assignee field without coding.
-
That won't work. You're saying that you want to have things on the board but not on the board at the same time, which obviously, you can't do.Think through the process - you create an issue, it lands in "To Do" status. You include it in a board, and eventually plan it into a sprint, and start that sprint. Your developers…
-
Really simple, and you've almost got yourself there already. Have a scrum board as you describe, and then create Kanban boards for the other users. The issues will all have the same workflows underneath them, and you can use the Scrum for all your planning. The Kanban boards will follow the same flow in the background, but…
-
Do you have the "space create" permission, and when you say "documentation space", how are you defining that? Is it a blueprint for a space? Have you got the right blueprints enabled?
-
There's a couple of things this could be, but let's start with the easy one: are all the issues on your board in the far right hand column?
-
There doesn't seem to be an actual question here? The error message you're getting there happens when the Tomcat running Jira is either dead already, not listening (have you changed the config?) or has failed. You need to read the catalina.out to find out what it's doing.
-
Ok, that's good, I don't think the data structure has changed for issues between those versions. So, I'd copy the xml to a new name (always backup...), go find 71001 in it and change it to 70107 :-)
-
Ahh, always fun that one. If the versions are quite similar (e.g. 7.0.1 and 7.0.4) then you can actually fiddle the build nnumber in the source xml and it'll work ok. What versions are we looking at here?
-
You should be able to use "project import" to drag in the content of a single project. See https://confluence.atlassian.com/jira/restoring-a-project-from-backup-185729444.html
-
Which add-on are you using to provide the coding function?
-
No. Re-indexing rebuilds the index which is a set of files on the application server. It does it by reading the database. It assumes that the database is the authoritative set of data for Jira (which is another reason to never touch it via SQL)
-
You can't. Not with the standard email handlers, they only do the basics. You need to find or write your own handler that can read your incoming email and deal with the extra fields you want to update. I always reach for JEMH when this question comes up, simply because it will do what you need.…
-
Go to the issue type scheme for your project, and remove "task" from it. It will vanish from the drop-down and you can throw away your validators too.
-
User macros are a restricted function on Cloud. You can write dynamic or static macros with Connect add-ons (see https://developer.atlassian.com/static/connect/docs/latest/index.html and look for dynamic/static)
-
Yes. You can integrate JIRA with almost anything. Start by defining what you want from "integrate"
-
No, a group is a collection of users. You can't nest groups. However, if you are using LDAP for an external user directory, you can do it in there. (Although the groups still look like sets of users in Confluence)
-
I'd take this one up with Atlassian support at https://support.atlassian.com - you'll need to go to them eventually to issue any refunds even if we could tell you more, so you might as well start there.
-
Yes, you should be able to create a screen with (just) the field "Linked issues" on it. The validation can kick in on the "validators" part of the workflow (although you'll want to do that on other workflow actions too)
-
I'd have said you "product defect blocks client bug" and "client bug blocks product defect" are both perfectly valid cases, but that's just picking at the edges of your description. In some cases, you can create nonsense and/or unhelpful links between issues. There is no validation built into JIRA, you'll need to find or…
-
Yes, true, but there is also the problem that the page presented before is not the same page after you commit the changes!
-
Yes, sorry, that's a bit vague - your browsing session contains a load of information from the page and what you did with it, and when you click "back", it's keeping it. Confluence presents it with a different page to what was there last time (because your edits have been saved) and that clashes with the information the…
-
I'm sure that could be done in the app - head over to https://jira.atlassian.com/browse/conf to raise it!
-
It's the data in the session information causing the edit issues. >It's intuitive to anyone who uses browsers that BACK should take you back to the previous location on a page, right? Yes, but the previous location as the browser sees it is the edit page. Because you're on the same page as the anchor. >Anyhow, could the…
-
On point 7, it's because you have not left the page - the browser is not recognising the anchor as a new url, it's stayed on the same page. The last change of url was from Edit mode to View, so the back button picks up the previous url - the edit page. 9-12 is a consequence of 7 - your changes are staying in the session…
-
The code given is for the Behaviours option, so you'd enter it in the add-on config screens.Post-functions are for writing data after the user commits the transition
-
Behaviours is a part of the "Script Runner" addon. Behaviours can do things to fields in the foreground before the user makes changes, rather than the post-function that would update data automatically after they commit. Which one is better depends very much on the goal. (This one sounds like a post-function)
-
Sorry converted that accidentally!
-
Ok, you'll need some code to do it (I would do it in the script runner as usual, although there are other scripting addons)You'll need to think about the second line too - is the status you are checking the before or after transition. You could actually drop it completely if you place the post-function in the right…
-
In what context? Are you defining a search? Or a post-function?