Comments
-
Ok, your automation is a separate thing, but you need to have the stories working before you can automate it really, so let's stick with that. Could you take a look at the three questions I asked a couple of comments ago?
-
You said the problem was that you could not move stories, not that you wanted to automate something. Automation like that requires code - you'll need to find or write something to do it.
-
Excellent. Last few questions * What columns are you trying to drag the stories from and to? * I'm pretty sure you've done this, but is the "in progress" status shared? i.e. both workflows use the same status for it? * Do your transitions have any "conditions" on them?
-
Ok, great, so I'm assuming the project is using CCAP workflow scheme, and the scheme says to use the workflows as their titles imply. Next step is a view of the board config - what status do you have in each column on the board?
-
I think there might be two separate parts to this question. First, there's the board behaviour - I'd like to skip that though, as I want to get the other stuff right, and make sure I fully understand what you've got set up. So, the workflows. You have two workflows, as per your question. I'm going to assume they are names…
-
Ok, most of that sounds right, you absolutely can have stories independent of tasks. As you've said, create two workflows, and use the workflow scheme to associate them with the different issue types. Issue types are independent of each other, so once you've got that setup, you will have independent flows for the two…
-
Ok, I can't see any way to do that in the view screen without some javascript hacking, but probably more important, I can't see any use for it. A button that shows a list in a document? Why?
-
I really don't understand this now. Could you tell me what you expect a confluence user to see when they are reading the page you want to add this to, and what they get when they edit it?
-
You said you already do above.
-
Sorry, I missed your last update. I think I can see what you're aiming for, but I don't see a use for it - a drop-down should provide a fixed list of options for a user to select from ( a user macro can implement those as options in its config) and a free-form url is a simple web-link that Confluence already supports. If a…
-
I'm sorry, I still really don't get what you're trying to achieve with this.
-
I still don't grasp what you're trying to do with a drop down or list - what are you expecting it to give to the user? When you put in a [ you should get a menu pop-up - that can help a user construct the right syntax for a link - it makes suggestions based on their recent history and allows for a search
-
Ok, I'm still lost on "dropdown" and "links" - a link is a free-form line of text that points to a resource somewhere else. A drop-down is generally a selection from a pre-set list of items. The [ link notation in confluence allows for links to be given names - for example Mr Flibble links back here, and it can point at…
-
A drop-down implies a pre-filled list, which doesn't really lend itself to links. Have you tried using simply the [ to create links?
-
I'm afraid that's far too vague and open question. We don't know what your setup is, or what problems you might encounter. * Read the release notes for 5.1 and 5.2 * Read the upgrade documentation * Try it on a test system. I'd also recommend investigating your existing errors - upgrading a system on top of a set of…
-
You'll need to set up a project mirroring system really - so that changes in one project on one server are replicated over to a similar project on the other. This can be a vastly complex thing to do, depending on how much you want to mirror and how the projects are configured. I have done it in the past, with scripts,…
-
Teamviewer, whatever that is, is not going to help - you need to understand your own installation and learn supporting it for yourself. The error you are getting could be anything, but you need to read the log file to find out what is going wrong. You haven't provided any information here about your setup, how your…
-
This is too little of the error message to be able to help you. You need to read the logs fully to work out what's going on here
-
Is your database definitely running on the same machine as Jira? We can't see that picture, it's not public (Generally, error messages in pictures are shortened and less useful forms - what's the text?)
-
I can't really. Your Jira server is unable to find your database server on your network. You need to fix your network lookups. Either the server doesn't have that name, or your DNS is not able to resolve it. Start with the basics - log into the Jira server and try "nslookup dbserver". If you don't get a valid response…
-
Basic networking - your database server is not called dbserver on your network (or, if it is, then your DNS is wrong and not resolving the name)
-
You need to join it to customfieldvalue although that still won't get you everything (another join to customfieldoption is needed) For lots more queries and detail on the schema, see https://developer.atlassian.com/display/JIRADEV/Database+Schema
-
The status change only happens if the workflow for the target issue type does not include the current status of the issue. Similarly for the fields - it will only offer you the fields you actually need to change during the issue type change. If you want to update other stuff, you have to do it as an edit, before or after…
-
You can download any version of JIRA from the downloads pages at https://www.atlassian.com/software/jira/download However, your old licence will only enable it to work if the release date of the version you choose is before the end date of your licence. If you get a new licence, you'll be able to use any version.
-
You could add Theme as an issue type, but it won't directly contain Epics or other issues at the same level - you would need to come up with a way of consistently telling JIRA that "this thing is part of that thing" and adjust your usage to take account of it. The "theme - sub-task" is not something I recognise, so it's…
-
System or Jira administrator rights are needed to configure fields. Sounds like the highest level you have is "project admin", so you'll need to talk to your admins.
-
Is it a scrum board?
-
It actually sounds like the screen schemes are probably right, and it's the fields that are failing. You say you are only getting "summary" on all the screens - I would guess that all the missing fields are custom fields? I suspect that you need to check two other places: 1. The field configuration scheme - you can hide…
-
Ah, I suspect this is the JIRA-Agile add-on or JIRA Software application. In projects that are Agile, it expects you to have an Epic link for stories. Not forced to use it, but it needs to be there if you have Epics
-
What does "field is always returning in the screen" mean? Returning from what?