Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per Project Activation ? #27

Open
BrunoSpy opened this issue Mar 16, 2017 · 3 comments
Open

Per Project Activation ? #27

BrunoSpy opened this issue Mar 16, 2017 · 3 comments

Comments

@BrunoSpy
Copy link

Would it be possible to activate this plugin as a module ?
Or another solution would be to restrict the field to some trackers.

@nanego
Copy link
Owner

nanego commented Mar 20, 2017

Hello Bruno
I think we could use it as a module in order to restrict the features to some projects.
We have always use it accros all our projects, but it would be a great option to add to the plugin.

@BrunoSpy
Copy link
Author

In fact I think the two options serve two different use cases.

  • Project module : some projects are totally independant and do not need the field
  • Per tracker : some trackers are project-related (for example we have trackers to follow risks and I don't think it's relevant to have the multiproject field)

As a consequence, I'll split the issue.

@da2125
Copy link

da2125 commented Nov 1, 2018

I've installed the redmine_multiprojects_issue plugin, (1st the two prereqs) but do I need to add a custom field, or anything else to get it to work? I'm on Redmine 3.4x but I just don't see the IMPACTED PROJECTS on any of my issues. Do I need to do anything to the issue itself? Are there additional steps required not described on https://github.com/nanego/redmine_multiprojects_issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants