系统地重命名项目任务列表，问题列表，文档库 [英] Systematically rename project Task list, issue list, document library

问题描述

您好，

我们最近完成的一个项目是让我们的客户跟踪他们的项目状态。对于他们运行的每个项目，都有一个项目任务列表，一个问题跟踪器和一个与之关联的文档库。

One of the projects we have done recently is for our client to track their projects status. For each project they run, there are a Project Task List, an Issue Tracker, and a Document Library associated with it.

例如，如果他们有一个名为ABC的项目，那么任务列表，问题跟踪器和名为ABC的文档库。

For instance, if they have a project called ABC, there is a Task list, an issue tracker and a document library named ABC respectively.

现在我们有需要  - 当客户重命名项目时，他希望系统系统地重命名任务列表，发布与该项目相关的跟踪器和文档库。 （意思是他不想更改名称3次 - 每个
用于任务列表，问题跟踪器和文档库）。

Now we have a need  - when the client renames a project, he'd like the system to systematically rename the task list, issue tracker and document library associated with that project. (meaning the he doesn't want to change the name 3 times - one each for the task list, issue tracker, and document library).

有人可以请帮助流失如何实现这一目标？

can someone please help shed some light how this can be accomplished?

谢谢，

J。

推荐答案

所有这些都在一个网站上吗？为什么我们使用单独的库/列表而不是使用元数据/查找来设置关系？我觉得你将来会为噩梦做准备。 

Are all of these in one site? Why are we using separate libraries/lists rather than using metadata/lookups to set a relationship? I feel like you're setting yourself up for nightmares in the future. 

如果你做了一个单独的库/列表方法一起由元数据分隔，你就不会有这个问题。

If you did a single library/list approach with all together separated by metadata, you wouldn't have this issue.

这篇关于系统地重命名项目任务列表，问题列表，文档库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！