I have a requirement to update the field on closed opportunities(won/lost) without reopening the records.
Please suggest if we do have any way of achieving this task.
Thanks.
Yes you can achieve this.
closed (Lost/Won) opportunity can be updated using workflow.
Create a OnDemand workflow which will update field which you wish and run this on closed opportunity.
try to see if you get field updated.
I just tried it on one of my instance for closed opportunity and I updated description field. It did updated without reopening opportunity.
Related
This question already has answers here:
Run Greasemonkey script on the same page, multiple times?
(2 answers)
How do I reload a Greasemonkey script when AJAX changes the URL without reloading the page?
(2 answers)
Closed 4 years ago.
Our recent upgrade from Jira Server v6.x to v7.x resulted in timestamps switching from absolute (24/Oct/18 11:37 AM) to relative (2 days ago) display. I know v7 has a global setting for relative vs. absolute timestamps but enough of my teammates like the relative timestamps that we can't make everyone happy with either system-wide setting. I'm trying to write a user script (for Tampermonkey) to fix the display in the browser. That way users who want absolute timestamps can get them without disturbing others.
I have the logic working. If I go to https://<myJiraServer>/browse/TICKET-123, all of the timestamps are processed. However, common scenarios leave timestamps unprocessed.
if I search for issues then click the issue key or summary to view issue details, the script doesn't seem to kick in.
if I refresh the resulting issue, the script runs but the back button doesn't get me to the search results.
if I shift-click the issue in the search results, the issue opens in a new window and the script runs
I've tried all the possible run-at settings but there seems to be something magic about how Jira replaces the search results page with the issue details that doesn't trip any of them. I wonder about injecting the script at document-start and having it rerun my processing with a timer or something. Any better thoughts?
This question already has an answer here:
How to delete test cases from Team Foundation Server
(1 answer)
Closed 7 years ago.
is there any way to remove completely a testcase from tfs 2012? I search for ways via google but it seems there is no way but maybe anyone has an special trick?
Test cases are work items. And work items can (with standard permissions) only be set to the state "Removed".
But you can "Destroy" a workitem from the commandline to eradicate it completely. The command is:
witadmin destroywi /collection:http://server:port/tfs/Collection /id:1
You can delete multiple work items in one go by passing a comma separated list to the id parameter
witadmin destroywi /collection:http://server:port/tfs/Collection /id:1,2,3,4
See also:
Remove workitems permanently
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
What is the sonar database structure?
Just want to ask which tables will be created after sonar get connected to the database? And also tables used to store the information like "Lines of code" "Classes" "Comments" etc. Could any one give me some documentation about these? Thanks
If you have a clean database with no tables, then Sonar will create all the required tables the first time you start it.
To know more about the tables, you can have a look at this DDL file that we are using for our tests:
https://github.com/SonarSource/sonarqube/tree/master/server/sonar-db-core/src/main/resources/org/sonar/db/version/schema-h2.ddl
The project split, but the 4.5.5 version of the DDL orginally linked in the answer can be found here:
https://github.com/SonarSource/sonarqube/blob/4.5.5/sonar-core/src/main/resources/org/sonar/core/persistence/schema-h2.ddl
In Redmine, is there a way to "temporarily close" a ticket so that it doesn't show up in most reports, but then have it re-open after awhile?
We have a status called "On Hold" which means it's still a valid issue, but we have no immediate plans to address it. It would be great if an "On Hold" issue could be closed for a specified period of time, say from 2-8 weeks.
I've made a feature request on the Redmine site, but I'm posting here because I'm interested in finding out if there's a way to do this already.
There isn't a way (using a standard install, anyway) to make those issues appear Closed without actually enabling the Issue Closed flag for that status, but a nice way to get them out of the way when viewing issue lists is to create a Custom Query from a search that excludes the ones you don't want, and then make that query public.
For example, I have a public custom query called "Not paused or complete" that excludes issues with a status of On Hold, Resolved, Closed, Declined. Any user can then apply this filter when viewing the issue list for a project, and it will show only active issues. Unfortunately, this won't affect reports such as roadmap reports - the issues will be shown the same as all other Open issues in these areas.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I am using subversion as an RCS and Bugzilla for issue tracking. And i just ask myself how to create automatic change logs for the users?
I already tried the "svn2cl" tool. But the change logs it creates are to technical for me (e.g. no user want's to know that developer XY changed 20 files yesterday to fix a memory leak). A user wants a change log which contains something like this:
Version 1.0- Added feature 1Version 1.1- fixed bug #4711- added feature 2...
Does anybody know a tool, addon or script to create change logs from my bugzilla entries? Or is there an good way to do this?
I know trac supports the creation of change logs, but i don't like trac very much.
Update
Wrote my own little tool for this job. You can get it at ChangelogGenerator.
There is a sourceforge project called Bugzilla Changelog which generate this log as HTML or Wiki - text.
See: Bugzilla Changelog Project
Using a custom tool which logs in a database changes per project, module etc. these changes are then exportable to files using a custom addin for finalbuilder for readme production, or exportable to a webservice which imports them into a local db for the webserver so users can view/search online what's changed per module.
i think you can have Bugzilla generate it for you.
Use the Advanced Bug Search screen, filter on the milestone / version, on the status and resolution.
Then you can export it as CSV format and work on it in Excel
Excel? :)
I'm assuming for each version you first create a list of features to implement, changes to make, bugs to fix etc. Somewhere the status of these must be tracked so you know what is complete, what has been pushed to a later version and so on, and when it's time to test and ship.
This information in your tracking document pretty much contains everything you need.