Comments
-
Fields are issue entities, not projects. So no, you can't add more "fields" to projects.
-
I would, but Atlassian have removed the documentation, replacing it with "how to do it with Data Centre" instead. The basic principles to start you off though: * Replicate the database in a master(rw)/slave(read only) config to standby server * Synchronise the attachments from production to standby server (do NOT sync…
-
Just for future reference, the templates within each "type" of project are useful, but they're only used at creation time, to guide what is initially created. They have no effect after the creation process. Personally, I find this wording a bit confusing, I would have preferred "type" to be called "Application-type" or…
-
I don't think Anup noticed the Trello tag or word in the question. Jira is a much older, more functional issue tracker / project management tool. Probably overkill for a lot of people, but your question sounds like you might be needing something more powerful than Trello.
-
It's not going to work, unless you are setting it up as a warm standby, and the load balancer is just there to select between production and standby.
-
Those two words are templates for project creation, not the types. The types of project are Core/Business, Software and Service Desk. If you edit the project, you'll see the type is probably Core/Business at the moment, so change that to Software to allow for Kanban (and other Agile) boards.
-
The most simple way to do this is go to create a new bug, and look to "configure fields" at the top right, then use the "where's my field" option, which will list why Story Points are not there.
-
Then the permissions in the project are against you. Are you sure you have transition issue, and there are transitions out of all the selected status, and no conditions, and no workflow properties?
-
If they can see the content, then there is no way to stop them getting it.
-
You'd need to ask Atlassian if they ever plan to implement any form of Connect framework to support it (which is very unlikely, as the trend for them is to go in the other direction to maintain supportability)
-
You need to be a Jira or System administrator to change the schemes. Although for this one, you need to amend the "issue type scheme", not the "issue type screen scheme"
-
>The recurrent trouble is that the issues don't reindex when it change it. Right, that is textbook "you have a broken Jira, but have ignored it and covered it up". Your regular re-indexing is hiding a deeper problem, and there is a good chance that this is at the root of your performance problems, or that the cause is…
-
You've probably already thought of this. To chain the subtasks, you will need to use your own scripts, but they're not too painful. At the moment, you've got a template (not sure how you're doing that, but it's not too important) that creates 7 sub-tasks. Change it so that it only creates the first one you want. You will…
-
There are three things that jump out at me: * In most cases, create the schemes you want, apply them to the projects, and you are done. The projects will behave the same. * Custom fields have a quirk in that they have "context" which is not handled by a scheme. You'll need to check that in the list of custom fields for…
-
It's not a "field", it's a list of valid transitions out of the current status. To change the list, edit your workflow.
-
Over REST, the response to a "get issue" can include all available transitions for that issue, including ID and name See https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/issue-getIssue
-
Edit the workflow, so you can see what screens are used by each transition. Go to the screens used and add the field (after checking the screens are *only* used by "close issue" type transitions)
-
Create a new scripted field as per normal custom field, then go to admin -> scripted fields. You'll then need to write a bit of code that does your calculation and returns Yes or No. Have a look at the script runner docs for some guidance on the coding.
-
Do you mean the system "resolution" field that is built in? If so, you don't need to do anything - just put the field on the close/resolve type transition screens and they will set it (Make sure you never put it on create or edit screens)
-
This sounds like some form of resource leakage on the browser side. Do you have any custom javascript? Can you try a different browser? Or better, a browser in "safe mode", with add-ons disabled?
-
Nope, you removed Confluence. Not the Confluence home directory. Try again.
-
No, it won't, it'll cause confluence to believe it needs to complete and install. "Broken" if you're trying to use a Confluence, but the point of the question was how to go back to an install cycle.
-
Filters looking for it will indeed stop behaving, but that's about it. The name of a resolution is very much a label on an underlying object.
-
Well, your query is already excluding a load of assignees. You'd need to find or write a new JQL function for "user has commented on this issue". The closest I can get without coding is to use a "participants" field from the Jira Toolkit - this will allow you to say "user has never commented and is not the assignee or…
-
Er, this is a 6 year old question and answer. Plus, scrubbing the <confluence home> directory will NOT remove the daemon start script - that's held in the startup script directories (On unix-like systems) and the installation directory (on Windows systems)
-
Generate a licence in that page, and go back to sourcetree to install it.
-
You'll need to add the user to a role that allows for "browse project" in each one. Or change the permission schemes. Yes you can do that via the admin UI, but one place at a time, not en-masse.
-
No. You can include the business project in an existing board, and swimlanes will work fine. But, that board cannot be the board for the business project, as business boards do not have swimlanes. It has to be a Scrum, Agility or Kanban board (with a filter that includes the issues from the business project)
-
Could you show us the list of existing issue types? (the line above "issue type schemes")
-
Your filter translates to "Open issues in RGSSD updated within the last 12 hours where the assignee is NOT <one of several people>" I am not clear on what you need to change in there? What are the conditions for people being included in that list?