Comments
-
You should now have "boards" in the menu bar, rather than "Agile"
-
As a project admin, go to version management, find it in the list and click "archive" You'll still get it in the search drop downs, but not when creating or updating issues.
-
>However, i do not see an option to enter all types of phones (for around 40 models we develop) This is a function of your data and usage. If there's data missing from drop-downs, your administrators need to add them. If you're completely missing somewhere to put the data, then you'll need to think about how you handle…
-
Define different screens and/or field configuration schemes for the different types of issues.
-
You can't run two things on the same port on the same server. You're going to need to do something with proxies for this. The really easy case is running a couple of services on different ports on the same server and using Apache to say "url X goes to port Y, and url Z goes to port A". Atlassian applications not only…
-
No, applications in this context, are things that run inside JIRA. You install JIRA on a server, then add Software and/or Service Desk applications to that. Add-ons are also added to JIRA in a similar way. But they're not JIRA Applications, they're still add-ons.
-
No. Service desk is an add-on for JIRA 6, and becomes an application in JIRA 7+. It is an "extra". See https://www.atlassian.com/software and note that there are three JIRA products there! Yes, you can migrate from Cloud to Server. The amount of effort is not generally huge, but there is always some.
-
I'd say stick with what you've got, if it worked before, then throwing it away and starting again is probable more work. Check your logs, and then think about increasing logging if the default logging doesn't help.
-
We don't know what escalation service you are using (the Jelly one that I wave at every time for example? Or a script runner? Something else?). Are you sure it's actually running? Is your filter returning the right results, or rather, any at all? When you say "it doesn't work", what does that mean? Does nothing at all,…
-
Of course it's going to affect them - the issues the boards are looking at are being changed. Remember that the boards are a view of core data, they're just showing you what you are doing to the issues in other boards. One thing that would probably help you here - only use scrum boards for the scrums. Your deployment board…
-
Your fourth board simply needs to filter for the issues you want in it. Change the board filter to find your issues.
-
Duplicate of https://answers.atlassian.com/questions/44355774
-
Yup, although it was with CentOS, and I can't claim any involvement on the OS side - as far as I could tell, I was handed a Linux box capable of running Java. Jira and Confluence ran fine on it.
-
It doesn't matter too much, as long as the number is unique within that workflow.
-
I'm afraid "cannot find the data that was imported" is not very informative. Could you explain that? Is just searching broken, or is the data not there at all? What data is missing? Can you see projects and users etc, but not issues? Does it look like an empty Jira completely, or is there something there? Could you also…
-
Very true - status is not a field, it's a display telling you where an issue is in the workflow. To re-open an issue via code, you need to do two things 1. Ensure the workflow has a transition from closed to open/reopened/whereever 2. Run the workflow transition. Obviously the API supports this (otherwise the web UI…
-
Gabrielle is doing exactly what the standard approach is. There's no "close project" function, as it's something you need to define for yourself really. So, you need to decide what your users can do in a "closed" project, build a permission scheme for it and apply it to your "closed" projects. Your main decision is…
-
I could do a bit, there are community members here who could do a lot more, my company certainly can help, but I suspect you're asking for help from Atlassian? Have you contacted https://support.atlassian.com ?
-
The best you can do for HA without data centre JIRA is a warm backup so that if the main node fails, you can switch over to the backup node relatively quickly. Replicate the database to a read-only slave, and use shared storage for the attachments. If it goes bang, make the slave a read-write master, start the backup JIRA…
-
No, that's not quite right. Incident and event have different workflows. Doesn't matter how similar they are technically, they're separate items. The scheme looks fine to me, which makes me think it's simply not associated with the right project(s)
-
I think you need to show us the workflow scheme you have and tell us what the issue types are. (Fields don't matter here)
-
In that case, you've not followed the steps in full. Check your workflow scheme maps your subtasks to workflows that you want, then that the scheme is associated with the project.
-
It's not brilliantly intuitive - I remember struggling with schemes when I started out. Especially screen schemes. This is the price we pay for flexibility :-)
-
Your sentences around what you've done with the workflow schemes seem a little confused. Jobin's given you the main link you need, but it's important to understand that what you need to do is: 1) Create a workflow scheme that says Issue types A, B and C use workflow 1 Issue types D and E (which are subtask types) use…
-
Um, not really, it depends entirely on your systems. I do have this in a cron on an old site though: #!/bin/bashwget https://yourjira/sr/jira.issueviews:searchrequest-excel-current-fields/10010/SearchRequest-10010.xls?tempMax=1000cp SearchRequest-10010.xls <somewhere> As you can see, it's not complex...
-
Code, if you want Jira to do it. A human can click "excel" as a view option on a filter and save it to a network share, or email it any time you want though. You might want to consider writing a script that will hit the excel url and do what you want, rather than trying to wedge it into Jira. (I've done it both ways - a…
-
Doesn't look like it. It says just JIRA 6.0
-
Then the project is not using that workflow scheme.
-
Ok, that answers it. Your story is not using the story workflow, it's set up to use the sub-task one. You'll need to fix the workflow scheme for the the project.
-
Ok, your setup should quite happily support that, so we need to look at what is blocking it. Can you pick a story that you don't seem to be able to drag between two of the columns (For example, one that's in Code Review and needs to go to QA). Could you then do these quick tests: * Pick up the card on the board. Does a box…