Comments
-
I meant why are you using iptables really.
-
Um. Why?
-
A workflow is exactly as you say - a map of a process built of status and transitions.The workflow scheme is how you tell a project which workflows to use. Many people use a 1:1, where all issues in the project use a single workflow, but the scheme let's you say "for bugs, use workflow 1, for features use workflow 6 and…
-
No, there isn't (unless you've done something really convoluted), you're still not looking at swimlanes.A swimlane goes across the board - they are *rows*, and they do NOT represent status (unless you've used JQL to make them do so, which is convoluted and pointless)A *column* is a column on the board. These represent the…
-
I think you've misunderstood swimlanes. Workflow is a set of steps or status through which an issue progresses. Agile allows you to map columns on to these (including the ability to have more than one status in a column, and not use the same names). Swimlanes cut across these columns, grouping your issues together by…
-
Have you got the time-tracking field on the create/edit screens for the sub-tasks?
-
Um, if it were "obvious", I would not have posted a link to an answer about something else. I'm not sure how to change the popup message box
-
Where you are in Jira is irrelevant, but to change the default timeout, see https://confluence.atlassian.com/display/JIRA/Changing+the+default+session+timeout
-
To echo Tim's point - you need to have Confluence offline, with a proven backup, if you're going to start messing with the database via SQL (which also renders you unsupported). Short story - don't.
-
You need a filter that will pull in the same data that all of their filters - (filter 1) or (filter 2) or (filter 3) and so-on.
-
A board is a view of a set of issues. So, you can create a new board and simply set the filter for it to include all the issues you want to see on it.
-
I suspect it's come from a Service Desk installation, but it could be something else. Could you let us know what version of JIRA Core you have, and whether you've got Service Desk and/or Software added to it.
-
I'm a bit out of my depth with javascript, so I can't help you there, but I did want to point out that Jira's built-in mandatory fields don't work like that. Their content is checked on the server side after the user commits a change.
-
Look at your original question - it says jira-administration and jira under the body in a pale blue box. Those are labels, or tags, or topics (just semantics of different words)
-
Ah, that's good background.It sounds like the version you've installed has some issues, and they probably need to go to Metova - the best way to raise this is probably with that last comment as a new question, tagged with addon-com.metova.jira.project-clone-plugin so that they get the emails triggered by using the label (I…
-
I think you need to explain a bit more.JIRA does not do "clone project", you had not mentioned an addon before, and we still don't know which addon you are talking about.At a guess, it seems like you have upgraded JIRA and whatever the addon is. I can't speak for the addon until I know which one it is.But JIRA's key…
-
What errors are you getting when you try to clone?
-
I suspect the problem is in "this doesn't work". You need to explain what your post-function code is doing and what error messages you get (if any). Then we might be able to tell you what you've got wrong in the code or assumptions you've made.
-
Ok, ignore that, you've edited the question to answer the original "don't want to code" point
-
You need to code for it if you want to copy estimates down to subtasks.
-
The way users are handled in 4.3 has changed - from a library called opensymphony to embedded crowd. You'll need to update your maven repositories/includes to make sure the Crowd library is available, and change any of your code that uses opensymphony users.
-
The way users are handled in 4.3 has changed - from a library called opensymphony to embedded crowd. You'll need to update your maven repositories/includes to make sure the Crowd library is available, and change any of your code that uses opensymphony users.
-
The way users are handled in 4.3 has changed - from a library called opensymphony to embedded crowd. You'll need to update your maven repositories/includes to make sure the Crowd library is available, and change any of your code that uses opensymphony users.
-
Er, you don't do upgrades by "using a database native tool to recover it" But, assuming that means you only used that to copy the data to a new place and then ran the actual upgrade process against it... How do you know that these issue ids are wrong?
-
Jira won't let you delete a user who has assigned or reported issues, so they couldn't have been on any issues. If you put them back with the same username, then they'll get back everything they had before, EXCEPT their groups and roles. (Jira only uses the email address to send mail to, it's not important as far as the…
-
You can't undelete a user, just re-add them as they were before.
-
I think those need to go to Atlassian!
-
Could you try the lexorank integrity checker and re-indexers? I cannot for the life of me remember the location, so log in as a full admin and use gg or the search for admin functions and start typing lexorank, you should see it pop out then.
-
It's a well buried option :-)
-
Er, you're mixing up text and html emails. Your first picture is a text email. The second is html. Change which you want to recieve in your profile.