Work Items Feature Related Across the project - azure

Is it possible to create two work items in different project but related each other ?
Description;
i mean Project 1 has a work item "ABC", and Project 2 has work item "ABC"
if I change state of my work item "ABC" from doing to done at Project 1, is it possible to have my work item "ABC" at Project 2 automatically change from doing to done as well?
looking for help
Thank you
Regards
Azh

If you only want to relate two work items and regardless of automatically change state, you can certainly relate two work items that are in different project. What you need to do is the same as relating two work items in the same project. You can refer to this document for detailed steps.
As of this time, however, the function of automatically change work items' state is not supported. But Microsoft have added the feature to their roadmap and offered an alternative solution. Please click this link for details and documentation.
There is a vote on this function in Developer Community, where you can follow the latest development of this feature.

Related

Event workflow in SharePoint

Clearly I need to edit my question.
If I'd like to create a process, a process for registering and handlig some kind of event inside an organisation, where you first register this event, by giving it a title, and some other properties (date, description etc), then this event should be handled in some ways, this will be done in several steps in order to resolve this event. What would be the best way to do this? I'm not looking for an answer in code, just a keyword for what this could be called, or a guide/tutorial, or a link to something similar.
All help is appriciated, if u don't understand my question please tell me, and I will try to elaborate.
Since you tagged this SharePoint, I assume you have a SharePoint site set up already. On that site, you want to create a list (either a calendar list or a custom list; try both and see which option has more columns you'll use, then add/remove columns until you're capturing all the data you need). Then you want to create a workflow (or workflows) that run on items created in that list. Workflows created in SharePoint Designer can do everything you're asking, from sending automatic emails to changing fields in your items. Googling "SharePoint workflows" will start you down the road to developing your solution.

Sharepoint MSS 2007 - Filtering mulitple inputs

I am building a directory tool that will list entries for technical support contacts and listed by its appropriate company. My end goal is to allow end users to be presented with 2 simple inputs, a drop down with the list of companies and a text input to enter the name of the technical team they would like to reach. Sharepoint has made this a nightmare.
Since my server is on MSS 3.0 I decided to use a form webpart where I have added created the 2 input (dropdown and text input). I made the parameters to point to the input and added them to the filters and finally made the webpart connection.
I was able to get as far as making a sucessful filter for the technical team but as soon as I try to filter by client the results are very sporadic and mostly incorrect. I play around with the list filter in Sharepoint designer 2007 tried to group the filters together, tried changing the AND/OR in every possible setting but no luck.
Decided to push it by creating a column named blank that basically had empty values. The idea behind that was to allow end user to leave the technical team input blank and show all entries for the company. I thought somehow it would have maybe solve my sporadic issue but instead made it more complex.
At this point I can probably live without being able to search with blank results but I need to be able to at least filter by company and technical teams. At this point any sort of help is appreciated, been at this for a few weeks and my project is due last week so I am pretty much desperate to solve this problem.
For those that may have a similar problem I have found a work around to this problem. I decided to use the ASP.net User Control and this works much better than the form webpart and provides much better results.
Here a link that I found which help me get me on the track:
http://blogs.msdn.com/b/sharepointdesigner/archive/2007/03/05/asp-net-controls-filter-the-data-view.aspx

Sharepoint 2010 - Datasheet view and 3 linked lists

I've got a tricky situation I'm trying to determine the best way to solve. I'm a VS developer who is learning SharePoint so it's a little frustrating to me when what I am trying to accomplish could easily be done with code and a db.
I have three lists, a parent and two children list that are linked through lookup columns. The client actually wanted everything in one list but due to SharePoint column type limitations I had to split the data into the three lists, there are over 300 fields. The client wants to see all the lists together in one view and be able to filter and edit groups of items.
I have successfully created a new data source linking the lists and can display that on one of my pages to view. After some research however I have learned that I can't create a datasheet view from this linked view due to limitations in the Office componets that SP uses. Which makes sense.
The business need is for the client to filter the three lists based on criteria they select from either list A AND list B and list C to get a group of items, they make the updates and save the changes back to the 3 lists. They prefer to do this in datasheet view because this mimics the excel spreadsheet that they are currently using that this website will replace. They will potentially be updating between 1-30 items at a time using this, which is why they prefer the drag and copy functionality.
I was thinking of two options: trying to create some kind of custom web part that has a gridview of all the columns in edit mode that they can filter down to their items and make their changes. Then I would have to loop through the fields and make updates programmatically. I also saw on this site jQuery.sheet, that looks like it may be a good solution if I go this route instead of gridview.
Or have a modal window with the columns listed, have the user select what they want to filter to, then redirect to a page that shows the three lists in their own DSVs. The user would have to make updates in the three separate views. Then I would use workflows to synchronize the lists after they had made their changes.
I always end up trying to do things programmatically since I am still largely unfamiliar with SP and only seem to hit its limitations instead of its strengths. Has anyone tried to do something similar to this? Or do you have any suggestions as to the best way to accomplish this? Best practices? I appreciate all thoughts and comments! FYI I've also posted this on the MS SP forums as well to cast a wider net...
Thanks,
Sabrina
In this case, you are better off going with a custom solution. A webpart would be an excellent choice for delivering your custom interface.
A dataview webpart will do the job, but if you feel comfortable with the jQuery solution it would make for a nicer interface.
In your code, treat the lists as you would a database and isolate it from the logic and interface code within the webpart.

Export list of Sitecore items as Excel (or other formats)

I noticed that sitecore has the option of exporting users in an Excel format.
I need to have similar functionality for exporting 'participations', (a users can enlist to take part in an 'event', and if their entry is approved via a sitecore workflow, a 'participation' item is created in the content tree)
Since mostly everything in Sitecore is in essence based on items, and I want to export items to Excel, my question is - what are some of the best ways of doing this?
Questions:
Is there a way to re-use this functionality for regular items?
Would it be a good idea to create a custom admin page (any tips on doing this?) which has some custom code that reads the items from the database using the API?
are there sitecore plugins/shared source projects that can help me achieve this?
Or does anyone have a better idea? - would it be better to just store the participations in SQL? I'm mostly doing it this way because I want to make use of the 'free' functionality offers, for example workflow, but if that leads to me using anti-patterns please shoot me ;)
Link is different now: https://marketplace.sitecore.net/en/Modules/Advanced_System_Reporter.aspx
P.S. Couldn't leave a comment to original answer as I don't have enough reputation. Oh well :)
Found a most excellent shared source module which does exactly this (and much more)!
Basically it allows you to configure (and easily extend, if you need to) any kind of table based report on 'items'.
The report module shows up as an application in the sitecore menu (like the user manager tool) and comes with features such as xml,csv, xls export. It's also really easy to set up, once you get the hang of it.
http://trac.sitecore.net/AdvancedSystemReporter

"Refresh" SharePoint site column definition on lists that use it?

We deployed a feature that installs a custom site column named "Classification." It is a Choice column type. Now, we need to change the choices. We can update the XML in the feature easily enough, but it doesn't affect any of the lists already used the existing site column; they still see the old choices.
Is there any way to send a refresh signal or something to the lists that use our Classification site column feature to have those lists use the updated choices?
I think the only way to archive this is by iterating each list that uses the column and change the XML there as the column within a list has no reference to the original column any more.
Flo has a point, and I have previously been working with this issue and have made a blog post that might help you out somewhat. Have a look:
http://johanleino.wordpress.com/2009/08/11/propagating-updates-to-content-types/
SharePoint can do this.. Don't change your feature but modify the created site column in each site collection through the web UI. Changes made this way will propagate.
(I hope you don't have 10.000 site collections ;)

Resources