What is the exact feature of Check in and Check Out in Document Management System(DMS).
I am little bit confuse with the 'in' and 'out'. Which functionality is actually for what.
In a system that manages documents, such as Nuxeo or LogicalDOC DMS the Check-in could also trigger versioning.
So it would produce a new version of the document using the latest file uploaded. Versioning allows to track changes in a document and get an earlier release.
Im not sure if this questions belongs here but in laymans term:
Check Out: is when you permit/disable access to a certain
module/document by any other program/user
Check In: is when you save your changes to the server and allow access to the document/module
Related
I am trying to allow users to create issues from a webpage, just like the Issue Collector. The problem is, there are only three templates provided for the collector and none of them are quite right.
What I want is to have three required fields that then combine to become the description. (Similar to how the first template has "what do you like" "what do you not like" which both go in the description)
The problem is there's no obvious way to edit the popup's contents.
Is there any way I can get at the source code of the collector to create my own modified version? Alternatively, if I just copy the html of the popup using inspect element could I create a working clone?
EDIT: Well, I've managed to get at the source code using a java decompiler, but now I haven't got a clue how to put it back together again...
Do you have a paid license for JIRA? If so, Atlassian will give you a copy of the source code.
From their FAQ's
After an order has been placed, how and when can the license key and source be accessed?
Access to your license key(s) and any
applicable source code is provided only after the successful receipt
and processing of your payment. Once payment is received, the Billing
and Technical contact specified on the order can log into their My
Atlassian account, and view all corresponding license keys.
And instructions on how to "put it all back together" :)
Then you are free to customize to your heart's content.
Of course, you'll need to re-customize every time there's an update from Atlassian ...
See also this post on Atlassian's wiki
New to TFS configuration/manipulation and looking to be pointed in the right direction thanks.
Our bug reports are often posted with minimal information and its often necessary to call the creator to get clarification. It would be beneficial if we could display the phone number alongside the creators name. Is it possible to pull this info out of the directory ?
I cannot think of a simple way of doing it, apart from writing code. I can think of these techniques:
pulling data from Active Directory and updating work items;
a custom control that query AD (via a REST web service) just in time
This latter can evolve to became a 2015 extension
My organization is moving away from JIRA and I've been given the task to archive or get all our JIRA tickets out ASAP. How can I do migration into any file/doc? any idea please as I can't find useful resource from the internet
Well you can perform an JIRA Backup that will generate you a backup which can be used to later restore but doesn't make it that useful in terms of viewing.
Or you can perform an issue search and from the results perform some sort of export:
Really depends on the number if issues you have, how custom your JIRA is and what useful data you wish to retain.
I have one folder in TFS and I have given rights as Contributor that's mean they can do check outs/check in/locks etc. But I would disallow them to delete any file or subfolder belonging to main folder. Please let me know if you have any idea in this regard.
You cant, but on the other hand a delete of a file only hides the file. In order to 'permanently delete' a file you need to run tf destroy on the file , and that requires the user to be a part of the tfs administrator group .
Read more here
You can't. I think this is something you will have to manage by process and not technology I'm afraid.
Any operation (excluding a destroy) can be undone.
As was already said, this can't be done with permissions. If you absolutely need a way to prevent this (and rolling back the delete afterwards is not enough), you have two possibilities:
use a Checkin Policy to warn the user that he should not delete elements. This can be overridden by the user, so it's not an absolute, but they know they may only do this with your permission. If they still check in without permission, you can still roll back. Biggest drawback: You need to distribute a dll file to all client PCs everytime the policy is changed, because the checkin policy is executed on the client.
set up a serverside pre-Checkin check. You can write against TFS API to react to different events, such as pre-Checkin, post-Checkin etc. In those event handlers you may perform checks, e.g. "is a delete operation contained in the changes the user wants to check in?" and make the operation fail if that's the case. This cannot be overriden by the user, but is a lot more effort to implement and maintain imho.
That said, I would propose setting up "checkin conventions" the users are supposed to adhere to, and roll back any changesets where they don't. Possibly supported by variant 1. to remind the user that what he is doing is not permitted.
Does TFS 2010 have the concept of checking out work items and checking them in. This action would lock the item for edit by other users while it is checked out.
I know I can do this for files under source control, but what about regular work items?
I haven't yet come across any documentation around this. If it's possible, does someone have a code sample?
That is not possible. In TFS11 we have added 'merge on save' so there are less conflicts when saving a work item.
Would love to know why you want this feature though.
You could achieve a lock mechanism on work items if you write a custom control that allows or denies saving based on the result of some query you make to a custom service.
You would want to create a visual studio plugin that sets and resets the lock per work item.
While you're at it, you could write a server plugin that persists a serialized copy if the work item to disk or to the version control system.
I know it's a lot if work, but it should give you what you asked for.